5 ms·
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 calculat
by JeremyBanks 15y ago
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.
- jrockway 15y agoYeah, but you know people want this so they can write things in their bug tracker like "fixed in r1232" instead of "fixed in 2c4d96d1dc2d12afd486561329a9a7b74d4ae110".
- mullr 15y agoThat's what `git describe` is for.
- JeremyBanks 15y agoI wouldn't mind "fixed in 981db17b8 (gen 1853)".
- stephen 15y agoThis will give you r/1232: https://github.com/stephenh/git-central/blob/master/server/post-receive-commitnumbers 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...)