From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
srabbelier <srabbelier@gmail.com>
Subject: Re: [PATCH] doc: technical details about the index file format
Date: Thu, 2 Sep 2010 09:28:44 +1000 [thread overview]
Message-ID: <AANLkTikOsZa6OvWkCV27NB7k2t+kT-5wDfx5Eaymx_MW@mail.gmail.com> (raw)
In-Reply-To: <201009012054.20482.robin.rosenberg@dewire.com>
2010/9/2 Robin Rosenberg <robin.rosenberg@dewire.com>:
>> + Entry path name (variable length) relative to top-level directory
> ...to the top level...
>> + (without leading slash). '/' is used as path separator. Special
> The special...
>> + paths ".", ".." and ".git" (without quotes) are disallowed.
>> + Trailing slash is also disallowed.
> Why would anyone even consider adding a trailing slash to a _file_ name?
Well, I was tempted to put directories in index more than once. And
subprojects are actually directories although they are treated as
files in index.
--
Duy
next prev parent reply other threads:[~2010-09-01 23:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 9:53 [PATCH] doc: technical details about the index file format Nguyễn Thái Ngọc Duy
2010-09-01 10:36 ` Ramkumar Ramachandra
2010-09-01 15:20 ` Sverre Rabbelier
2010-09-01 18:54 ` Robin Rosenberg
2010-09-01 14:39 ` Nguyễn Thái Ngọc Duy
2010-09-02 8:56 ` Alex Riesen
2010-09-02 9:08 ` Joshua Juran
2010-09-02 14:50 ` Junio C Hamano
2010-09-02 15:11 ` Erik Faye-Lund
2010-09-06 10:37 ` Nguyễn Thái Ngọc Duy
2011-02-19 22:16 ` Sverre Rabbelier
2011-02-20 9:30 ` Nguyen Thai Ngoc Duy
2011-02-26 10:03 ` Nguyen Thai Ngoc Duy
2011-02-26 10:23 ` Junio C Hamano
2011-02-26 13:36 ` Nguyen Thai Ngoc Duy
2011-03-02 1:51 ` Junio C Hamano
2011-03-02 3:34 ` Nguyen Thai Ngoc Duy
2011-03-02 6:02 ` Junio C Hamano
2011-03-02 11:43 ` Nguyen Thai Ngoc Duy
2011-03-02 12:53 ` Drew Northup
2010-09-01 23:28 ` Nguyen Thai Ngoc Duy [this message]
2010-09-02 5:59 ` Robin Rosenberg
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=AANLkTikOsZa6OvWkCV27NB7k2t+kT-5wDfx5Eaymx_MW@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robin.rosenberg@dewire.com \
--cc=srabbelier@gmail.com \
/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 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 NNTP newsgroup(s).