With svn the the IDs are unique in, so r123 implies a branch. svn log
—revision=123:234 give the right change list when svn is directed at that
branch. So right now, I can get the change list in one command easily without a
script.
llvmlab bisect already encodes branch information in the build
Sequential IDs are important for LNT and llvmlab bisection tool.
LNT uses the “order” to capture the measured software changes. LNT does make
the assumption that orders are unique, so if a ID was the same on two branches,
LNT would assume that is the same change. If you never want to compare d