git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiang Xin <worldhello.net@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] git apply: binary files differ can be applied with -pN (N>1).
Date: Wed, 24 Nov 2010 14:53:39 +0800	[thread overview]
Message-ID: <4CECB673.9090809@gmail.com> (raw)
In-Reply-To: <4CECA0AE.90505@gmail.com>

How to reproduce the bug:

1. Generate a patch file against two directory with binary diff.
================================================================

$ mkdir hello-1.0 hello-2.0

$ dd if=/bin/ls of=hello-1.0/binary.dat count=1 bs=32
1+0 records in
1+0 records out
32 bytes (32 B) copied, 0.00121276 s, 26.4 kB/s

$ dd if=/bin/ls of=hello-2.0/binary.dat count=1 bs=64
1+0 records in
1+0 records out
64 bytes (64 B) copied, 0.00030288 s, 211 kB/s

$ git diff --no-index --binary hello-1.0 hello-2.0 > patch.txt

2. The patch file has patch level 2
===================================

$ cat patch.txt 
diff --git a/hello-1.0/binary.dat b/hello-2.0/binary.dat
index dc2e37f81e0fa88308bec48cd5195b6542e61a20..bf948689934caf2d874ff8168cb716fbc2a127c3 100644
GIT binary patch
delta 37
hcmY#zn4qBGzyJX+<}pH93=9qo77QFfQiegA0RUZd1MdI;

delta 4
LcmZ=zn4kav0;B;E

3. Apply the patch failed
=========================

$ cd hello-1.0

$ git apply --check -p2 ../patch.txt
fatal: git diff header lacks filename information when removing 2 leading pathname components (line 3)


于 2010年11月24日 13:20, Jiang Xin 写道:
> When patch file generated against two non-git directories using
> 'git diff --binary --no-index' without '--no-prefix', the patch
> file has patch level greater then 1, and should be applied with
> '-p2' option. But it does not work if there are binary differ
> in the patch file, it is because in one case the patch level is
> not properly handled.
> 
> Signed-off-by: Jiang Xin <jiangxin@ossxp.com>
> ---
>  builtin/apply.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/builtin/apply.c b/builtin/apply.c
> index 23c18c5..d603e37 100644
> --- a/builtin/apply.c
> +++ b/builtin/apply.c
> @@ -1126,6 +1126,7 @@ static char *git_header_name(char *line, int llen)
>  	 * form.
>  	 */
>  	for (len = 0 ; ; len++) {
> +		int nslash = p_value;
>  		switch (name[len]) {
>  		default:
>  			continue;
> @@ -1137,7 +1138,7 @@ static char *git_header_name(char *line, int llen)
>  				char c = *second++;
>  				if (c == '\n')
>  					return NULL;
> -				if (c == '/')
> +				if (c == '/' && --nslash <= 0)
>  					break;
>  			}
>  			if (second[len] == '\n' && !memcmp(name, second, len)) {


-- 
蒋鑫

北京群英汇信息技术有限公司
邮件: worldhello.net@gmail.com
网址: http://www.ossxp.com/
    http://blog.ossxp.com/
电话: 010-51262007, 13910430470
传真: 010-51262007

  reply	other threads:[~2010-11-24  6:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24  5:20 [PATCH] git apply: binary files differ can be applied with -pN (N>1) Jiang Xin
2010-11-24  6:53 ` Jiang Xin [this message]
2010-11-24 17:20 ` Junio C Hamano
2010-11-25  1:46   ` Jiang Xin
2010-11-25  2:52     ` Jiang Xin

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=4CECB673.9090809@gmail.com \
    --to=worldhello.net@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).