per...@pluto.rain.com (Perry Hutchison) writes:
Junio C Hamano gits...@pobox.com wrote:
Olsen, Alan R alan.r.ol...@intel.com writes:
I found an interesting bug in git-format-patch.
Say you have a branch A. You create branch B and add a patch to
it. You then merge that patch into branch
example of what is happening here.
-Original Message-
From: Perry Hutchison [mailto:per...@pluto.rain.com]
Sent: Monday, November 26, 2012 8:15 PM
To: gits...@pobox.com
Cc: git@vger.kernel.org; Olsen, Alan R
Subject: Re: Interesting git-format-patch bug
Junio C Hamano gits...@pobox.com
I found an interesting bug in git-format-patch.
Say you have a branch A. You create branch B and add a patch to it. You then
merge that patch into branch A. After the merge, some other process (we will
call it 'gerrit') uses annotate and changes the comment on the patch that
exists on branch
Olsen, Alan R alan.r.ol...@intel.com writes:
I found an interesting bug in git-format-patch.
Say you have a branch A. You create branch B and add a patch to
it. You then merge that patch into branch A. After the merge, some
other process (we will call it 'gerrit') uses annotate and changes
Junio C Hamano gits...@pobox.com wrote:
Olsen, Alan R alan.r.ol...@intel.com writes:
I found an interesting bug in git-format-patch.
Say you have a branch A. You create branch B and add a patch to
it. You then merge that patch into branch A. After the merge,
some other process (we will
5 matches
Mail list logo