git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: A Large Angry SCM <gitzilla@gmail.com>
To: "Santi Béjar" <sbejar@gmail.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>, git@vger.kernel.org
Subject: Re: git/gitweb - feature request: Add description to the branches.
Date: Tue, 06 Sep 2005 10:33:49 -0400	[thread overview]
Message-ID: <431DA8CD.9060009@gmail.com> (raw)
In-Reply-To: <87ll2aib73.fsf@gmail.com>

Santi Béjar wrote:
[...]
> 
>         One thing I'm missing is a way to describe a branch. It can be
>         done in the $GIT_DIR/description, the first line for the whole
>         repository and the rest for the branches. So description file
>         for the git.git repository could be:
> 
> [description]
> The core git plumbing
> pu: Proposed updates
> rc: Release candidate
> todo: Todo list
> [/description]
> 
>         And it can be added to the gitweb tool.

Having somewhere to describe the intent of a branch would be a useful 
convention. But I think the descriptions should be in separate files; 
one for each branch and one for the repository as a whole.

That way it would be possible to have long, multi-line descriptions of 
the repository and branches with the tools displaying just the first 
line unless more information is requested; like gitk and gitkweb do with 
commit messages.

An unrelated gitweb feature request: include a timestamp near the top of 
the projects page so that I don't have to try to remember when I last 
reloaded the page. TZ=UTC preferred.

  reply	other threads:[~2005-09-06 14:34 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 [this message]
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

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=431DA8CD.9060009@gmail.com \
    --to=gitzilla@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kay.sievers@vrfy.org \
    --cc=sbejar@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).