From: Don Zickus <dzickus@redhat.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] apply: fix copy/rename breakage
Date: Thu, 10 Jul 2008 11:43:48 -0400 [thread overview]
Message-ID: <20080710154348.GC22201@redhat.com> (raw)
In-Reply-To: <48762919.6070902@viscovery.net>
On Thu, Jul 10, 2008 at 05:22:01PM +0200, Johannes Sixt wrote:
> >> With this patch, we disable the postimage record 'fn_table' when applying
> >> a patch to produce new files out of existing file by copying to fix this
> >> issue.
> >
> > Odd. I guess the way I read this workflow is
> >
> > apply change X to A, copy A' to B, apply change Y to B => B' now has changes X+Y
> >
> > But instead you are saying B' only has change Y because A is copied to B
> > not A'.
> >
> > Regardless, it doesn't affect my workflow.
>
> Oh, it does. It's a normal git diff where a copy was detected!
>
> Don't let you distract by the word "incremental" and by the names A and B.
> In the example above, the change X comes first because 'A' is sorted
> before 'B'. If the roles of A and B were swapped, then you have this patch:
>
> diff --git a/A b/A
> copy from B
> copy to A
> --- a/A
> +++ b/A
> ... change text Y here ...
> diff --git a/A b/B
> --- a/A
> +++ b/B
> ... change text X here ...
>
> See?
Yes, thank you!
Cheers,
Don
prev parent reply other threads:[~2008-07-10 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 3:10 [PATCH] apply: fix copy/rename breakage Junio C Hamano
2008-07-10 3:13 ` Junio C Hamano
2008-07-10 4:21 ` Stephan Beyer
2008-07-10 14:01 ` Don Zickus
2008-07-10 15:22 ` Johannes Sixt
2008-07-10 15:43 ` Don Zickus [this message]
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=20080710154348.GC22201@redhat.com \
--to=dzickus@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=torvalds@linux-foundation.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).