From: "John Rigby" <jcrigby@gmail.com>
To: git@vger.kernel.org
Subject: binary patch compatibility
Date: Wed, 1 Nov 2006 14:03:28 -0700 [thread overview]
Message-ID: <4b73d43f0611011303m3e58b227x1a0bd60a9719f9f8@mail.gmail.com> (raw)
If I commit a new binary file to a repository and then use
git-format-patch --binary to produce a patch the resulting patch file
is not compatible with the patch command.
Am I doing something wrong or is this not possible.
Thanks
next reply other threads:[~2006-11-01 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 21:03 John Rigby [this message]
2006-11-01 21:10 ` binary patch compatibility Jakub Narebski
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=4b73d43f0611011303m3e58b227x1a0bd60a9719f9f8@mail.gmail.com \
--to=jcrigby@gmail.com \
--cc=git@vger.kernel.org \
/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).