Re: What's in git.git

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Nov 12, 2006, 22:25 UTC
Message-ID: <Pine.LNX.4.63.0611122319340.13772@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <Pine.LNX.4.63.0611072009220.2601@qynat.qvtvafvgr.pbz>

Hi,

On Tue, 7 Nov 2006, David Lang wrote:

Show 14 quoted lines

> On Tue, 7 Nov 2006, Junio C Hamano wrote:
> 
> > [pu]
> > 
> >  Johannes's shallow clone work now should rebase cleanly on top
> >  of 'master' although I haven't done so yet.  As he said
> >  himself the series is waiting for people who have needs for
> >  such a feature to raise hands.
> 
> I haven't been watching this recently, but if this is what I understand it to
> be (the ability to get a partial repository from upstream and work normally
> from there with the result of data-mineing tools sometimes reporting 'that's
> part of the truncated history' if they hit the cutoff) consider my hand
> raised.

For now, it does not say "part of the truncated history". But yes, shallow clones are partial copies of remote repositories, by making some commits "shallow", i.e. grafting an empty set of parents onto them (thereby pretending that these commits are root commits).

Telling the user that a commit is shallow should not be too hard.

Ciao, Dscho