From: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Shallow clone [Was Re: What's in git.git ]
Date: Wed, 08 Nov 2006 23:29:05 +0530 [thread overview]
Message-ID: <45521AE9.7050902@gmail.com> (raw)
In-Reply-To: <45520872.3090506@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
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
[-- Attachment #2: repository-layout.txt.diff --]
[-- Type: text/x-patch, Size: 537 bytes --]
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.
next prev parent reply other threads:[~2006-11-08 17:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 3:21 What's in git.git Junio C Hamano
2006-11-08 4:13 ` David Lang
2006-11-08 16:40 ` Shallow clone [Was Re: What's in git.git ] Aneesh Kumar K.V
2006-11-08 17:59 ` Aneesh Kumar K.V [this message]
2006-11-09 4:04 ` Shallow clone Junio C Hamano
2006-11-09 4:17 ` Aneesh Kumar
2006-11-11 13:57 ` Alexandre Julliard
2006-11-12 8:16 ` Junio C Hamano
2006-11-12 17:59 ` Sergey Vlasov
2006-11-12 21:59 ` Junio C Hamano
2006-11-13 5:29 ` Junio C Hamano
2006-11-12 13:12 ` Shallow clone [Was Re: What's in git.git ] Petr Baudis
2006-11-12 20:04 ` Shallow clone Junio C Hamano
2006-11-09 2:28 ` What's in git.git Horst H. von Brand
2006-11-09 2:54 ` Junio C Hamano
2006-11-09 3:04 ` Junio C Hamano
2006-11-09 3:45 ` Dave Dillow
2006-11-12 22:25 ` Johannes Schindelin
2006-11-08 7:40 ` Jakub Narebski
2006-11-08 7:59 ` Junio C Hamano
2006-11-08 7:58 ` Jakub Narebski
2006-11-08 8:26 ` Junio C Hamano
2006-11-08 14:51 ` Petr Baudis
2006-11-09 0:02 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45521AE9.7050902@gmail.com \
--to=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).