Thread (1 message) 1 message, 1 author, 2016-06-15

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

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

Johannes Schindelin [off-list ref] writes:
Hi,

On Tue, 1 May 2007, Junio C Hamano wrote:
quoted
Nicolas Pitre [off-list ref] writes:
quoted
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.
Of course, you could graft a fake relationship there. Something like

echo $(git rev-parse master master^ next) >> .git/info/grafts

should do. And you can do it _locally_, since all you care about is the 
higher-level relationship that _you_ know about. And this is the way to 
teach Git about it.
In case you did not get it, making the above usable is not about _me_.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help