> > But still, is there not an easy way to determine that a changeset only > > exists in the trunk and not in any branch? Is this a feature of svnmerge > > (which I have yet to try).
> A revision number in subversion can be considered as an instant > snapshot of the whole repository, so one cannot think in term of > whether a revision "exist or not" in a branch. A revision may contain > changes that have occurred in one branch or another, but each revision > applies to the repository as a whole. Moreover, a branch is nothing > more than a path in Subversion (whereas they are distinct objects in > ClearCase) I don't think I ever said or implied that I was looking for a revision. I am trying to track a changeset. A changeset is made one place (branch) and then merged to other places, no? And each merge and commit creates a new revision. Back to the original (hypothetical) problem. I determine that the bug that my customer just reported is fixed in changeset 1234. How do I determine what version to give him that has this fix? It may be fixed in the trunk. It may be fixed in a branch. It may have been merged. How do I determine this? JLM --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
