[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7vaa84t3ek.fsf@alter.siamese.dyndns.org>
Date: Thu, 10 Nov 2011 07:15:15 -0800
From: Junio C Hamano <junio@...ox.com>
To: Johan Herland <johan@...land.net>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
"Ted Ts'o" <tytso@....edu>, Shawn Pearce <spearce@...arce.org>,
git@...r.kernel.org,
James Bottomley <James.Bottomley@...senpartnership.com>,
Jeff Garzik <jeff@...zik.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-ide@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git patches] libata updates, GPG signed (but see admin notes)
Johan Herland <johan@...land.net> writes:
> On Wed, Nov 9, 2011 at 18:26, Junio C Hamano <gitster@...ox.com> wrote:
>> - "git notes" is represented as a commit that records a tree that holds
>> the entire mapping from commit to its annotations, and the only way to
>> transferr it is to send it together with its history as a whole. It
>> does not have the nice auto-following property that transfers only the
>> relevant annotations.
>
> True. However, consider these mitigating factors:
> ...
>
> My point is that although "notes" might end up transferring more
> annotations than strictly necessary, I believe that in practice all the
> notes being transferred are already (or will soon become) relevant.
Sorry, but I do not think you are considering what would happen when you
have many branches with different purposes, whose commits near tips will
never get merged with each other. "automatic following" semantics like
what "git fetch" does for signed tags is absolutely necessary in such a
case, and the above are not mitigating factors at all in that context.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists