#git bot interface

History of !revision_numbers

• Revision numbers are often requested, but no matter what algorithm you choose to generate them, they cannot simultaneously have all four desirable properties: (a) increasing (b) unique (c) immutable [for a given commit] (d) decentralized. Subversion obviously does not need (d). Git uses a hash function, and thus gets all but (a). See man gitrevisions for other ways to refer to commits.
  By charon at 2013-06-07 13:44:07
• Revision numbers a la Subversion are often requested, but no matter what algorithm you choose to generate them, they cannot simultaneously have all four desirable properties: (a) increasing (b) unique (c) immutable [for a given commit] (d) decentralized. Subversion obviously does not need (d). Git uses a hash function, and thus violates property (a) but gets the others. See man gitrevisions for other ways to refer to
  By charon at 2013-06-07 13:43:38
• Revision numbers a la Subversion are often requested, but no matter what algorithm you choose to generate them, they cannot simultaneously have all four desirable properties: (a) increasing (b) unique (c) immutable [for a given commit] (d) decentralized. Subversion obviously does not need (d). Git uses a hash function, and thus violates property (a) but gets the others.
  By charon at 2013-06-07 13:39:21
• Revision numbers a la subversion are often requested, but no matter what algorithm you choose to generate them, they cannot simultaneously have all four desirable properties: (a) increasing (b) unique (c) immutable [for a given commit] (d) decentralized. Subversion obviously does not need (d). Git uses a hash function, and thus violates property (a) but gets the others.
  By charon at 2013-06-07 13:39:07
• Revision numbers a la subversion are often requested, but no matter what algorithm you choose to generate them, they cannot simultaneously have all four desirable properties: (a) increasing (b) unique (c) immutable [for a given commit] (d) decentralized. Git uses a hash function, and thus violates property (a) but gets the others.
  By charon at 2013-06-07 13:38:17
• Revision numbers a la subversion are often requested, but no matter what algorithm you choose to generate them, they cannot simultaneously have all four desirable properties: (a) increasing (b) unique (c) immutable [for a given commit] (d) decentralized. Git chooses to use a hash function, and thus violates property (a) but gets the others.
  By charon at 2013-06-07 13:37:46
• Revision numbers a la SVN: pick any three of (a) nondecreasing (b) unique (c) immutable for a given commit (d) decentralized. Git's sha1 hashes satisfy all but (a).
  By charon at 2013-06-07 13:31:27