> Now, it's true that this design mostly came from the days when we were > mainly thinking about Subversion as a backend. There, all the revisions > numbers are identical between difference repositories, but of course a > r100 in one repository has nothing in common with a r100 in another > repository, so in this case it's necessary to "qualify" which repository > one is talking about. Not so with Mercurial and Git, where you can be > reasonably confident that e.g. a changeset f1f422a1053e in one > repository would be *exactly* the same as a changeset f1f422a1053e if > that one is found in another repository (a clone for example). So yes, > in the latter case, it would make sense to be able to specify only the > changeset number and let Trac find the appropriate changeset among the > active repositories.
In my case, I have a trac project that's based off a new project whose trunk was svn mv'd from a branch on a different project. I loaded the wiki and tickets from the other project, and we're in the process of deleting bugs from both projects that are no longer applicable. We then have two problems with changesets, where it would be nice if trac could figure out which repo has which changeset. One is that all the old tickets refer to the changesets in the original project, which is visible to trac, but the changesets aren't clickable because the default repo doesn't have those changesets. The other issue is that history browsing is broken: trac can't walk back in history between the two repos. svn log shows the revisions correctly for the files, but since trac doesn't see the changesets in the primary repo, and it doesn't know that the secondary repo is a valid place to look, it doesn't allow me to traverse into the other repo. If there were some way I could unify the changesets in trac to allow smart choosing based off a changeset number, I would think that would help my case. I don't think what I've done is common enough to be of general use, but it would at least be nice for me. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
