News for hackers. Stuff that matters.

A comment on Beautify the Git commit hash (have a look at the commit hashes on the right). Parent comment

Re:Beautify the Git commit hash (have a look at the commit h... by JeremyBanks on Saturday October 01, 2011 @08:28PM (#3061609)
You have duplicates, B and C would have the same generation number. It just represents length of the longest path from the root commit. This is already calculated internally to optimize several operations, so they were considering making it part of the commit data.

It often won't uniquely identify commits, but revision numbers in SVN are also sometimes used imprecisely ("oh, it was around R1500"), so I think it would have value.

[ Parent | on HN ]
Re:Beautify the Git commit hash (have a look at the commit h... by jrockway on Saturday October 01, 2011 @08:29PM (#3061612)
Yeah, but you know people want this so they can write things in their bug tracker like "fixed in r1232" instead of "fixed in 2c4d96d1dc2d12afd486561329a9a7b74d4ae110".
[ Parent | on HN ]
Re:Beautify the Git commit hash (have a look at the commit h... by stephen on Sunday October 02, 2011 @12:47AM (#3062097)
This will give you r/1232:

https://github.com/stephenh/git-central/blob/master/server/p...

(It makes a tag-per-commit; I'm not saying that's necessarily a good idea, but if you really want revision numbers...)

[ Parent | on HN ]
Re:Beautify the Git commit hash (have a look at the commit h... by JeremyBanks on Saturday October 01, 2011 @10:26PM (#3061824)
I wouldn't mind "fixed in 981db17b8 (gen 1853)".
[ Parent | on HN ]
Re:Beautify the Git commit hash (have a look at the commit h... by mullr on Saturday October 01, 2011 @09:25PM (#3061727)
That's what `git describe` is for.
[ Parent | on HN ]