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

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: May 1, 2007, 17:42 UTC
Message-ID: <Pine.LNX.4.64.0705011939590.4010@racer.site>
In-Reply-To: <7vps5k5uzt.fsf@assigned-by-dhcp.cox.net>

Hi,

On Tue, 1 May 2007, Junio C Hamano wrote:

Show 20 quoted lines

> Nicolas Pitre <nico@cam.org> writes:
> 
> > 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.

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.

Ciao, Dscho