Re: git am and duplicate signatures

Joe Perches writes: > On Tue, 2016-08-30 at 11:17 -0700, Junio C Hamano wrote: >> Joe Perches writes: >> >> > >> > On Tue, 2016-08-30 at 10:41 -0700, Joe Perches wrote: >> > > >> > > Maybe something like traces or chains. >> > Or "taggers" or "tagged-bys"

Re: git am and duplicate signatures

On Tue, 2016-08-30 at 11:17 -0700, Junio C Hamano wrote: > Joe Perches writes: > > > > > On Tue, 2016-08-30 at 10:41 -0700, Joe Perches wrote: > > > > > > Maybe something like traces or chains. > > Or "taggers" or "tagged-bys" > I am afraid that you are way too late; the ship

Re: git am and duplicate signatures

Joe Perches writes: > On Tue, 2016-08-30 at 10:41 -0700, Joe Perches wrote: >> Maybe something like traces or chains. > > Or "taggers" or "tagged-bys" I am afraid that you are way too late; the ship has already sailed a few years ago, if not earlier, I think.

Re: git am and duplicate signatures

(adding lkml) On Tue, 2016-08-30 at 09:54 -0700, Junio C Hamano wrote: > Joe Perches writes: > > git-am -s will avoid duplicating the last signature > > in a patch. > > > > But given a developer creates a patch, send it around for > > acks/other signoffs, collects signatures

Re: git am and duplicate signatures

Joe Perches writes: > git-am -s will avoid duplicating the last signature > in a patch. > > But given a developer creates a patch, send it around for > acks/other signoffs, collects signatures and then does > a git am -s on a different branch, this sort of sign-off > chain is