Scott Palmer wrote:
> On Jan 2, 2005, at 5:30 AM, allan juul wrote:
>> Scott Palmer wrote:
>>> Why not just treat 'tags' the same as 'trunk'.. add the subprojects
>>> directly under 'tags', then put the project specific bits in that
>> thanks for the suggestion. we might end up doing something like that.
>> but actually my biggest concern right now is the fact that apparently
>> i can *not* just tag in a single svn command. this is also hard to
>> believe when i think of other version control systems where one "just
>> do it". [eg. 'cvs tag tagname module']. one doesn't have to be
>> bothered about directory structures. i know subversion has a different
>> perspective of tags and branches but to me it's very important that
>> tagging [or branching for that matter] is just something you do (in a
>> single command) and that's it. in out case Tagging will be done very
>> very frequently and to ask people to create subdirectories (one by
>> one) before they eventually can tag is simply too much hassle IMHO.
> Just create the tags/subproject/ folder at the same time you create the
> trunk/subproject folder. From that point on making a tag for that
> project is still a single command.
the problem in our case is that projects most likely will be created in
trunk only since developers will add these on a day-by-day basis. i dont
want hassle them to also create a project in the tags directory. i just
wish they could do:
$ svn copy URL/whatever/trunkURL URL/whatever/morewhatever2/tagURL
and not think about it anymore. it is so easy to do elsewhere ;)
hmm, i'll post another related question in a second to see if it's
possible at all ...
> Or you could re-think your repository structure and use the alternative:
> structure. The flexibility is there to find something that will fit how
> you like to work.
you are right. that won't fit [perfectly] in our case for various
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Jan 2 21:15:48 2005