info too quick to pick a path to initial revision

[Matthew Fuller]

info -v shows a 'first revision' for the branch history, but it's too quick to limit itself to a single path back to null. In a branch I have here:

% bzr info -v | grep first ; bzr log -r1 | grep ^timest
   first revision: Thu 2008-07-24 17:35:39 -0500
timestamp: Mon 2003-08-11 22:03:03 +0000

The timestamp it gives for 'first revision' is correct in a sense; this branch has 2 'initial' revisions. So any single 'first revision' line is necessarily going to be a partial truth. I tend to think that picking the initial rev on the mainline is the most bzrish thing to do, but picking the oldest of all the choices would be better than just picking the first one we find.

[Matthew Fuller (fullermd)]

I just hit this again on another branch, that _doesn't_ have multiple parentless revs. It just goes down a very long-lived branch and picks the first rev down that side, despite the fact that it's a child of and older rev sitting right there on mainline.