[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Labeling techniques

From: Gavin Lambert <gavinl_at_compacsort.com>
Date: 2005-12-20 01:46:00 CET

Quoth Phil Endecott <mailto:spam_from_subversion_users@chezphil.org>:
> Erik, why is it important to you that the revision number
> doesn't change when you change the status of a file? It seems
> like an unnecessary restriction to me. Perhaps you are putting
> too much value on the repository revision number. It is just a
> number.

I think what Erik was hinting at was this sort of scenario:

1. Commit some changes to a group of files as revision #245.
2. QA group updates to revision #245 and begins testing.
3. Commit some other changes (potentially overlapping) as revision #246.
4. QA group approves revision #245, and wants to mark all changes in it
as approved (or possibly even approve some changes and deny others) --
but they don't want to approve anything that happened in #246, and AFAIK
property changes can only be made to the HEAD revision...?

If this is the case, then I think branching is the way you'll have to
go. Copy revision #245 to an "approved" branch; once #246 is tested and
approved, merge those changes in too. And so forth.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 20 02:07:22 2005

This is an archived mail posted to the Subversion Users mailing list.