Thread (3 messages) flat view 3 messages, 3 authors, 2016-06-15

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

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:07

Nicolas Pitre [off-list ref] writes:
On Tue, 1 May 2007, Junio C Hamano wrote:
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help