Re: Tags and branches handling

Hi Stefan and thank you.

The reason I want to tag only changed files is because we will create small
depoyment packages and rollback packages only to a live webenvironment.
Tagging the hole directory will tag files not changed for a release aswell
and that is not what we want. We want to be able to see in an easy way what
files was released where and when. The packages we create will contain only
changed files that we will replace in the live env.

I'm actually thinking of a new approach now.

Why use tags at all in each project in a repository? Instead we could create
a global (toplevel folder in repository) tags directory where we copy only
changed files and name them after release and what the revision currently is
at (release1.0_rev15). Inside each project instead of tagging we just
compair revisions. I like the idea that you can ask subversion repo "how did
you look in revision 14"

The question is how to in an easy way ask Subversion. Give me all changed
files in all projects from revision 14.?

Thanks

--
View this message in context: http://www.nabble.com/Tags-and-branches-handling-t1258801.html#a3349003
Sent from the tortoisesvn - dev forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org