From: A Large Angry SCM <gitzilla@gmail.com>
To: cel@citi.umich.edu, Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] GIT Repository Annotation Convention
Date: Thu, 08 Sep 2005 14:32:34 -0400 [thread overview]
Message-ID: <432083C2.6080704@gmail.com> (raw)
In-Reply-To: <43207B68.5020204@citi.umich.edu>
Chuck Lever wrote:
> yay! are you also proposing some git tools to deal with these? it
> would be great to have some version control (keep these like generation
> files so we can see the history of revisions).
>
> A Large Angry SCM wrote:
>> GIT Repository Annotation Convention
[...]
I'm not proposing any new tools, just a convention that existing tools
or tools that others may create can adopt to provide information to a
repositories users. Some existing tools that could use the annotations are:
git-branch
git-show-branch
gitweb
There are likely others.
Like any other file under $GIT_DIR, these files are not automatically
versioned. Rather, each repository maintainer, needs to decide how a
repository's meta-data (project meta-meta-data) is tracked or generated.
prev parent reply other threads:[~2005-09-08 18:32 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
[not found] ` <43207B68.5020204@citi.umich.edu>
2005-09-08 18:32 ` A Large Angry SCM [this message]
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=432083C2.6080704@gmail.com \
--to=gitzilla@gmail.com \
--cc=cel@citi.umich.edu \
--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 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).