Re: [PATCH] git-bundle - bundle objects and references for disconnected transfer.

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 15, 2007, 15:35 UTC
Message-ID: <Pine.LNX.4.63.0702151632270.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <45D3C1DB.9020009@verizon.net>

Hi,

On Wed, 14 Feb 2007, Mark Levedahl wrote:

Show 26 quoted lines

> Johannes Schindelin wrote:
> > 
> > On Wed, 14 Feb 2007, Mark Levedahl wrote:
> > 
> > > Mark Levedahl wrote:
> > > > Johannes Schindelin wrote:
> > > > 
> > 
> > I don't think you need the bases. If you say "master~10..master" on 
> > the sender side, you want to update master on the receiving side, 
> > _after_ you verified that receiver already has "master~10".
> > 
> git>git-rev-parse master~10..master
> dc0f74905bd94b88d3b1d477e79faef7e0308fbf
> ^602598fd5d8f64028f84d2772725c5e3414a112f
> 
> Which shows the new head and the commit that the destination needs. That 
> is fine. But:
> 
> git>git-rev-parse master --since=10.days.ago
> dc0f74905bd94b88d3b1d477e79faef7e0308fbf
> --max-age=1170641182
> 
> is not helpful: it does not tell what is expected to be on the other 
> end. And I find both forms absolutely useful in the ways I use 
> git-bundle.

You're right.

But instead of doing this with Python or by hand, why not make the "--boundary" option useful in that case?

> I have found in practice my current solution of git-fsck to be much 
> faster.

It is only faster since you unpack the objects. Which makes almost every other operation slow.

Ciao, Dscho