From: Christian Hesse <mail@eworm.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] replace binary keyrings with armored keys
Date: Sat, 13 Dec 2014 20:30:21 +0100 [thread overview]
Message-ID: <20141213203021.7bec320e@leda.localdomain> (raw)
In-Reply-To: <xmqq1to4y1uy.fsf@gitster.dls.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
Junio C Hamano <gitster@pobox.com> on Fri, 2014/12/12 13:50:
> Christian Hesse <mail@eworm.de> writes:
> > Last but not least git and patch can handle this a
> > lot better.
>
> Actually we can handle binary patch just fine ;-)
Ah, that was kind of misleading. :-p
Generating a patch with git including binary data and trying to apply with
patch results in something like "git binary diffs are not supported".
Anyway... Thanks for applying!
--
Best regards,
Chris
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-13 19:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 13:16 [PATCH v2 1/1] create gpg homedir on the fly and skip RFC1991 tests for gnupg 2.1 Christian Hesse
2014-12-11 22:41 ` Junio C Hamano
2014-12-12 8:47 ` Christian Hesse
2014-12-12 8:50 ` [PATCH 1/3] create gpg homedir on the fly Christian Hesse
2014-12-12 8:50 ` [PATCH 2/3] skip RFC1991 tests for gnupg 2.1 Christian Hesse
2014-12-12 8:50 ` [PATCH 3/3] replace binary keyrings with armored keys Christian Hesse
2014-12-12 18:36 ` Junio C Hamano
2014-12-12 20:42 ` Christian Hesse
2014-12-12 21:50 ` Junio C Hamano
2014-12-13 19:30 ` Christian Hesse [this message]
2014-12-12 8:52 ` [PATCH 1/3] create gpg homedir on the fly Eric Sunshine
2014-12-12 8:55 ` Christian Hesse
2014-12-12 18:26 ` Junio C Hamano
2014-12-12 20:33 ` Junio C Hamano
2014-12-12 20:45 ` Christian Hesse
2014-12-12 20:33 ` Junio C Hamano
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=20141213203021.7bec320e@leda.localdomain \
--to=mail@eworm.de \
--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).