Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?

From: Shawn Pearce <spearce@spearce.org>
Date: Nov 21, 2006, 18:39 UTC
Message-ID: <20061121183941.GB22283@spearce.org>
In-Reply-To: <456330CD.9080503@freescale.com>

Timur Tabi <timur@freescale.com> wrote:

Show 16 quoted lines

> Shawn Pearce wrote:
> >Timur Tabi <timur@freescale.com> wrote:
> >>>Shallow clone is a development feature still being working on in
> >>>Junio's 'pu' branch of git.git.  It has a few issues still to be
> >>>worked out so it hasn't been made part of one of the more stable
> >>>branches yet (like 'next', 'master', or 'maint').
> >>Well, until it's available on an official git release, it doesn't help me.
> >
> >One of the reasons its hanging out in 'pu' still is that there is
> >a lack of people who are interested in the feature, and thus not
> >enough people are testing it.  Perhaps you might be able to lend
> >a hand in that regard?
> 
> Sure, I can do that!  Can you give me some pointers?  I've never done 
> development on git itself, so I don't know Junio or his pu (sorry, I 
> couldn't resist :-)).

Junio C Hamano is the Git maintainer. His published Git repository is here:

	http://www.kernel.org/pub/scm/git/git.git/

though it oddly has pack files from Jun 2006 in the wrong directory. Weird. Anyway...

If you clone from that URL, or better though the native Git protocol:

	git://www.kernel.org/pub/scm/git/git.git

you will get a branch called `pu`, which is the set of "Proposed Updates" to Git that Junio and others are currently working on. You can then checkout a branch off that, and build it:

	git checkout -b pu-build pu
	make

finally you can either run from that directory (see INSTALL file) or you can install the binary somewhere else. We don't really recommend using `pu` for production level work, so make sure you have a backup of any repository you run it on. :)