Re: cvs revision number -> git commit name?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxx>
www.herland.net
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]