From: Aneesh Kumar K.V Date: Wed, 08 Nov 2006 17:59:05 GMT Subject: Re: Shallow clone [Was Re: What's in git.git ] Message-ID: <45521AE9.7050902@gmail.com> In-Reply-To: <45520872.3090506@gmail.com> Aneesh Kumar K.V wrote: > David Lang wrote: >> 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. >> >> there are a number of cases where I would be interested in following a >> project as it moves forwards, but do not have the need to have the >> full history (even with the good compression that a git pack provides, >> it's still a significant amount of disk space and download time for >> large projects) >> > > I am trying to test this feature. Is there a documentation .git/shallow > some where. Atleast what those entries > mean ? I know in the mail johannes mentioned only core git will touch > this file. But it should be ok to be descriptive like other files. > (FETCH_HEAD) How about this -aneesh diff --git a/Documentation/repository-layout.txt b/Documentation/repository-layout.txt index 275d18b..03a6f77 100644 --- a/Documentation/repository-layout.txt +++ b/Documentation/repository-layout.txt @@ -141,3 +141,9 @@ logs/refs/heads/`name`:: logs/refs/tags/`name`:: Records all changes made to the tag named `name`. + +shallow:: + Records the sha1 of the commits which is marked to have no + parents to represent a shallow repository.The commit object + will have the parent information present. It carry one + record per line.