git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Paul Franz <thefranz@comcast.net>
Cc: git@vger.kernel.org
Subject: Re: Attributes for commits
Date: Sat, 9 Jun 2007 20:48:51 +0200	[thread overview]
Message-ID: <200706092048.52142.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <466AA714.4050500@comcast.net>

lördag 09 juni 2007 skrev Paul Franz:
>     I am a ClearCase administrator and one of the things that I love 
> about it is the ability to assign attributes to versions of files. Is 
> there anybody thinking of adding the ability to assign attributes to a 
> commit? I ask because I was thinking about how I would move from 
> ClearCase to git and part of our process is to assign the BugNum 
> attribute to every checkin so that we can see what bugs have been fixed. 
> We also track the files checked in the bug tracking software to. Thus 
> giving us a two way linkage between repository and the bug tracking 
> system. This is VERY useful. And I was wondering if there are any 
> thought to this for commits.
> 
> Now, I will be honest it is possible that this has already been done (I 
> have not read all the documentation yet) and I am justing wasting 
> bandwidth. In which, please excuse my ignorance and tell me to just RTFM.
> 
> Paul Franz
> 

We use the convention of putting the bug number as the first work on the first line of
the checkin, e.g. "3399 Add attributes for commits". The advantage over other methods
is that it is always there, without the need to further investigations of assigned attributes.

This convention has nothing to do with Git though. It works with any type of repo.

-- robin

  parent reply	other threads:[~2007-06-09 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-09 13:11 Attributes for commits Paul Franz
2007-06-09 13:49 ` Johan Herland
2007-06-09 18:48 ` Robin Rosenberg [this message]
2007-06-10  2:10   ` Paul Franz

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=200706092048.52142.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=thefranz@comcast.net \
    /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).