3 ms·
Two points: 1. You can abbreviate the SHA-1's in git 2. When you are collaborating on code, it's much more common to use a global identifier so that people ca
by pyre 17y ago
Two points:
1. You can abbreviate the SHA-1's in git
2. When you are collaborating on code, it's much more common to use a global identifier so that people can all know which commit is being referenced. It seems like you are making things needlessly complex when you are trying to maintain local and global revision numbers, for little (in my opinion) return. Sure 'r37' is easier to remember off-hand than '5b98d8f' (a shortened SHA1), but if you memorize 'r37' it only means something locally, you'll still have to lookup the global revision id when you want to communicate with others.