On Fri, May 13, 2011 at 10:40 PM, Niels Sascha Reedijk <niels.reedijk@xxxxxxxxx> wrote: > a - b - c - d - h > \ e - f - g / > > Now I invite you to tell me whether haiku/master-4-g1234567 refers to > changeset 'd' or 'f'. What if you "linearize" it like a - b - c - d - e - f - g - h, assuming the e - f - g branch was merged before h. Of course this wouldn't make much sense in the sense that revision numbers wouldn't exactly represent time, but it would be stable in the sense that a merge would not change previous (b's c's and d's) revision numbers. So a bug ticket's revision number would stay correct even after a later merge. Btw, in terms of matching SVN's revision numbers, this should be easy given that when the switch happens, SVN's revision numbers will map 1-to-1 with git/hg's. And that should represent revision numbers seen in bug reports until the switch occurs. -- Hike Danakian