From: A Large Angry SCM <gitzilla@gmail.com>
To: git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] GIT Repository Annotation Convention
Date: Fri, 09 Sep 2005 10:24:48 -0400 [thread overview]
Message-ID: <43219B30.4040308@gmail.com> (raw)
In-Reply-To: <7vvf1bq64t.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> A Large Angry SCM <gitzilla@gmail.com> writes:
>
>>Junio C Hamano wrote:
>>>A Large Angry SCM <gitzilla@gmail.com> writes:
>>>
>>>>Naming and Directory Structure
>>>>------------------------------
>>>>Annotations are named by appending ".txt" to the basename of the
>>>>repository component it describes, and by appending ".dir" to each
>>>>directory patch component leading to the repository component from
>>>>$GIT_DIR, and by prepending "annotations/" to the annotation pathname.
>>>I suspect you can do the same without .dir but only with .txt.
>>Think about a directory containing directories "foo" and "foo.txt":
>
> And where do you see foo.txt under $GIT_DIR/ hierarchy?
Are you saying I can't name a branch "foo.txt"? Or have the following
branches?
$GIT_DIR/refs/head/WidgetSoft/Blue
$GIT_DIR/refs/head/WidgetSoft/Red
$GIT_DIR/refs/head/WidgetSoft.txt/Blue
$GIT_DIR/refs/head/WidgetSoft.txt/Red
next prev parent reply other threads:[~2005-09-09 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 13:21 git/gitweb - feature request: Add description to the branches Santi Béjar
2005-09-06 14:33 ` A Large Angry SCM
2005-09-08 1:27 ` Junio C Hamano
2005-09-08 16:03 ` [RFC] GIT Repository Annotation Convention A Large Angry SCM
2005-09-08 18:00 ` Junio C Hamano
2005-09-08 18:58 ` A Large Angry SCM
2005-09-11 16:37 ` Matthias Urlichs
2005-09-11 18:08 ` A Large Angry SCM
2005-09-12 0:26 ` Horst von Brand
2005-09-13 17:46 ` Matthias Urlichs
[not found] ` <43208110.6020607@gmail.com>
[not found] ` <7vvf1bq64t.fsf@assigned-by-dhcp.cox.net>
2005-09-09 14:24 ` A Large Angry SCM [this message]
[not found] ` <43207B68.5020204@citi.umich.edu>
2005-09-08 18:32 ` A Large Angry SCM
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=43219B30.4040308@gmail.com \
--to=gitzilla@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.
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.