Re: [PATCH 0/8] git-repack --max-pack-size

From: Junio C Hamano <junkio@cox.net>
Date: May 1, 2007, 17:11 UTC
Message-ID: <7vps5k5uzt.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <alpine.LFD.0.98.0705011044210.6574@xanadu.home>

Nicolas Pitre <nico@cam.org> writes:

Show 9 quoted lines

> On Tue, 1 May 2007, Junio C Hamano wrote:
>
>> I was not sure if that is even a good idea, and I am now
>> inclined to think that keeping the failed attempt history is
>> probably better than potentially causing confusion to people who
>> follow 'next'.  But it _is_ a possibility to reset 'next' to
>> 'master'.
>
> And what is the advantage of doing that, exactly?

Not much and that is why I am not sure if that is a good idea, but one thing is:

	$ git log master..next
	$ git log --no-merges master..next

would start showing what are still pending in next without noise.

With the current 'next', the output of the former is almost useless, and the latter is useful only until 'next' starts diverging again from the master and if you are interested in what will never merged to 'master'. Once 'next' starts growing again, you will get mixture of what's cooking and what's killed; the output from the latter would become useless again.