Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #2021

Closed
Open
Opened Oct 07, 2010 by Karsten Loesing@karsten

Remove binary diffs from Git's commit mails

Whenever I add/remove/move binary files in Git, the commit mails contain the full binary diff. These binary diffs bloat the commit mails and aren't useful at all.

What? You say, there shouldn't be any binary files in Git anyway? But... what about libraries and generated PDFs? Don't belong there... can't hear you!

Sebastian says that commit mails are formatted using git-format-patch:

git-format-patch --subject-prefix="$projectname/${refname#refs/heads/}" \
--stdout "$oldrev..$newrev" |

I wonder if we can add --no-binary to this line to display a notice that files changed, but without showing the diff.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#2021