From: "Shawn O. Pearce" <spearce@spearce.org>
To: Caio Marcelo <cmarcelo@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: Binary files in format-patch
Date: Mon, 5 May 2008 19:01:53 -0400 [thread overview]
Message-ID: <20080505230153.GL29038@spearce.org> (raw)
In-Reply-To: <d280d7f10805051555x67bd7e87o999a2c9e19663b92@mail.gmail.com>
Caio Marcelo <cmarcelo@gmail.com> wrote:
> I'm using "git format-patch" to generate messages for a code review
> mailing list. It work fine except when we have binary files involved.
> Their contents are not relevant for us, and doesn't help much in a
> mailing list. Taking a peek at the code I've found out this:
Why then are they committed in Git and being modified? If the
files aren't relevant, why are they tracked?
--
Shawn.
next prev parent reply other threads:[~2008-05-05 23:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 22:55 Binary files in format-patch Caio Marcelo
2008-05-05 23:01 ` Shawn O. Pearce [this message]
2008-05-05 23:10 ` Caio Marcelo
2008-05-06 9:19 ` Robin Rosenberg
2008-05-08 20:21 ` Caio Marcelo
2008-05-08 20:25 ` Caio Marcelo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080505230153.GL29038@spearce.org \
--to=spearce@spearce.org \
--cc=cmarcelo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).