Knowing that it is in "trunk" does not tell you what version is in trunk at that time without looking. Its easy enough to check the revision of the tag of the last release.
--Noah On Oct 3, 2007, at 1:38 PM, Jeremy Mordkoff wrote: > >>> He knew the changeset number. It should be simple to map a changeset >>> number to a branch. > > >> There are no branch for Trac 0.11, as Trac 0.11 has not been >> delivered >> yet. The trunk contains the latest development version of Trac. Once >> Trac 0.11 is released, a new Trac 0.11-stable branch will be created, >> and official releases of Trac will be tagged from this branch. >> The trunk will become the current dev. branch for the next release - >> 0.12 - as soon as Trac 0.11 is delivered. > > > Okay, I get it. In clearcase, 'main' (which is normally the equivalent > of svn's 'trunk') is also a branch, albeit a special one. > > 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). > > 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 -~----------~----~----~----~------~----~------~--~---
