Re: [PATCH] Add git-bundle: move objects and references by archive.

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 19, 2007, 15:03 UTC
Message-ID: <Pine.LNX.4.63.0702191557580.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <erc8nm$feg$1@sea.gmane.org>

Hi,

On Mon, 19 Feb 2007, Mark Levedahl wrote:

Show 13 quoted lines

> "Johannes Schindelin" <Johannes.Schindelin@gmx.de> wrote in message
> news:Pine.LNX.4.63.0702190126220.22628@wbgn013.biozentrum.uni-wuerzburg.de...
> > Hi,
> > 
> > Sorry to be such a PITA, but I really, really think that it is wrong to
> > make a tar dependency here. You said your cygwin has problems with binary
> > files. Could you please try this:
> > 
> > $ echo -ne '\x1a\x1b\x15\x10\0abc' | cat | wc
> > 
> Same result on Cygwin and FC6:
> ~>echo -ne '\x1a\x1b\x15\x10\0abc' | cat | wc
>      0       1       8

Okay, so I really would like to have the bundle file from this experiment:

Show 8 quoted lines

> To repeat an earlier message, I tried the following:
> 
> cat bundle | (
>      while read <header stuff> do
>        <prcess header stuff>
>      done
>      git-pack-index --stdin
> )

because I cannot see how the aforementioned "cat" can succeed, while pack-index --stdin cannot.

> A bundle file *is* an archive.

But the archive in the bundle really is the pack. You don't need any other archive there. You don't need to know the name of the prerequisites file, for example, if that information is in the header to begin with.

> </unsolicited ignoreable gripe>Has anyone considered how much easier all 
> of git would be if it were written in c + python, rather than c + every 
> variant of shell + core utils + non-core utils known to mankind since 
> the dawn of unix?</unsolicited ignorable gripe>

You realize that Python can be a PITA, a real PITA, when it comes to non-Linux systems?

Just look at the fun we had with subprocess. It is included in Python 2.4, _works_ with Python 2.3, but _not_ Python with 2.2. If you now say "well, just upgrade!" then I SHOUT at you. There is _no_ excuse forcing users to upgrade when the failure is on _your_ part.

Ciao, Dscho