git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Herland <johan@herland.net>
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Cc: git@vger.kernel.org, Aaron Crane <git@aaroncrane.co.uk>
Subject: Re: cvs revision number -> git commit name?
Date: Wed, 27 Jan 2010 23:19:30 +0100	[thread overview]
Message-ID: <201001272319.30134.johan@herland.net> (raw)
In-Reply-To: <hbf.20100127jjbx@bombur.uio.no>

On Wednesday 27 January 2010, Hallvard B Furuseth wrote:
> Johan Herland writes:
> > You could consider adding the CVS revision numbers as notes (see "git
> > help notes" in >= v1.6.6) to the corresponding commits. Then they don't
> > pollute the commit messages, but instead live in a separate, but
> > parallel hierarchy that can be easily pulled in when you need to
> > reference them (e.g. GIT_NOTES_REF="refs/" git log).
> 
> Thanks, looks better than munging the log.  Though with one common
> weakness - should likely omit noting mass commits, since they'd clutter
> what 'git log' displays too much.  Of course, either could used combined
> with a mapping table.

Of course, you wouldn't put the cvs revision numbers on the default notes 
ref ("refs/notes/commits"). You would rather put them on a _different_ notes 
refs (e.g. "refs/notes/cvs"), where they would not clutter you "git log", 
and then when you _need_ to look at them, you simply run:

  GIT_NOTES_REF=refs/notes/cvs git log


...Johan

-- 
Johan Herland, <johan@herland.net>
www.herland.net

      reply	other threads:[~2010-01-27 22:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 21:53 cvs revision number -> git commit name? Hallvard B Furuseth
2010-01-26 22:53 ` Aaron Crane
2010-01-26 23:43   ` Johan Herland
2010-01-27  8:38     ` Junio C Hamano
2010-01-27 11:28       ` git notes issues (was: cvs revision number -> git commit name?) Johan Herland
2010-01-27 17:47     ` cvs revision number -> git commit name? Hallvard B Furuseth
2010-01-27 22:19       ` Johan Herland [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=201001272319.30134.johan@herland.net \
    --to=johan@herland.net \
    --cc=git@aaroncrane.co.uk \
    --cc=git@vger.kernel.org \
    --cc=h.b.furuseth@usit.uio.no \
    /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).