Re: [PATCH] built-in tar-tree and remote tar-tree

From: Sven Ekman <svekman@yahoo.se>
Date: May 19, 2006, 21:43 UTC
Message-ID: <20060519214318.38240.qmail@web25910.mail.ukl.yahoo.com>
In-Reply-To: <7v7j4ik1fr.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <junkio@cox.net> skrev:

Show 6 quoted lines

> Sorry for sending a crapoid that does not even
> compile.  I ran format-patch while on a wrong 
> branch.
> 
> Tonight's "pu" will have a fixed up one for 
> people who are interested to play with.

Hi Junio,

Thanks for your answer. I'm looking forward to try the remote tar-tree at the weekend. While this will definitely make it much more easy to grab single revisions out of a git tree, it only solves a part of the issue I was trying to address. If one wanted a simple snapshot of the source, it's usually easier to download a tarball.

The great thing about having the kernel source in a git repository is that it lets me upgrade the kernel source tree in place with a single simple command. No firing up a browser, downloading and applying a patch. It is also braindead easy to maintain a set of local patches across different kernel versions. Git makes all this quick and easy.

Is there a simple way to retrieve a single object or a list of objects _without_ any of their parents? If so one could retrieve the wanted commit and the corresponding tree and parse it on the client side to retrieve its descendents and commits. If so, the number of roundtrips would be roughly proportional to the depth of the trees, which would probably still be acceptable.

Greetings, Sven