• hg changeset ID locality

• Sudden realization: There is a possibility of an hg repo closely following another one to lose sync of changeset IDs (contrary to changeset hashes which are unique). Committing in both, pulling to each other and merging creates different intermediate IDs. I need to remember looking at the chanset ID in the upstream Tx repo before linking to the changeset when closing tickets.

• μεσάνυχτα, Σάββατο 2 Αυγούστου 2008
  [ Mini-post, Tech/web, Transifex ] | Σύνδεσμος | Σχολιάστε!

1 σχόλιο »

1. • #1
   • Giorgos Keramidas
   • ξημερώματα, Κυριακή 3 Αυγούστου 2008

   • Yep. The only “unique” identifier of a changeset is the full sha256 hash :D

     You can get hold of the sha256 changeset ID by referring to the ‘{node}’ in output templates like the one below:

     $ hg tip --template '{node} | {date|age} | {desc|strip|firstline}