From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: Shallow clone
Date: Sun, 12 Nov 2006 12:04:42 -0800 [thread overview]
Message-ID: <7vodrcctyd.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20061112131209.GC7201@pasky.or.cz
Petr Baudis <pasky@suse.cz> writes:
> On Wed, Nov 08, 2006 at 06:59:05PM CET, Aneesh Kumar K.V wrote:
>> 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::
>
> Hmm, shouldn't the shallow file rather belong to the info/ subdirectory?
I think that makes sense.
next prev parent reply other threads:[~2006-11-12 20:04 UTC|newest]
Thread overview: 25+ 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
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 ` Junio C Hamano [this message]
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
[not found] <CAEfjWpHhLKpghGRFtzstndk_vYMkLSLAGfXx8agoQmakC-6Otg@mail.gmail.com>
2014-08-19 11:11 ` Fwd: Shallow clone Steven Evergreen
2014-08-19 12:01 ` Duy Nguyen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vodrcctyd.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.