Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Good. So what happens when I checkout that tag and then make a change and commit? Am I committing to the trunk or the branch? (... some time going by before I hit send while I'm thinking about this and remembering someone in a reply to one of my posts said you can only commit on branches not on tags...) So I guess if you need a certain release because you need to add more fixes to it, then you need to checkout that branch at that specific release. But I can't see you needing a specific tag of a branch unless: 1. You just need to build it. 2. You intend to create a new branch at that specific tag. I can't see you needing the tag to make bug fixes in that branch since you would always apply bug fixes at the tip. Thanks, Nick "Tony Hoyle" <tony.hoyle at march-hare.com> wrote in message news:ebpoc1$bql$1 at paris.nodomain.org... > Nick Duane wrote: >> Can I set a tag on a branch and have that tag visible without having to >> specify that branch? What I mean is let's say I fix all the bugs in the >> branch and tag it as t-3-8-rtm. Does someone need to know the branch if >> they want to get this release or can they just specify the tag and get >> that release? > > A tag references a specific revision which may or may not be on a branch, > so when you checkout t-3-8-rtm you get that exact revision wherever it > came from. > > Basically, checking out a tag will always get you exactly the same file > that you tagged, no matter what has happened since. > > Tony