Yeah, thanks! Your answer is along the lines of what I've been thinking. Using the repo browser or hook-script. Best would probably be to introduce a hook script which forbids people to branch from an older version than was previously branched. An example of such a script would be GREATLY appreciated! Changes can otherwise get lost in production...
--- Den ons 2010-06-30 skrev Bob Archer <bob.arc...@amsi.com>: Från: Bob Archer <bob.arc...@amsi.com> Ämne: RE: out of date branches Till: "Jan Lund" <janne_l...@yahoo.com>, "users@subversion.apache.org" <users@subversion.apache.org> Datum: onsdag 30 juni 2010 17:55 > -----Original Message----- > From: Jan Lund [mailto:janne_l...@yahoo.com] > Sent: Wednesday, June 30, 2010 11:28 AM > To: users@subversion.apache.org > Subject: out of date branches > > Hi all, > > I would like to know if there are any recommendations as to enforce > a team to always branch from the latest revision of a branch. > There's a big risk that a developer might have forgotten to update > a branch, then does a replace (in TortoiseSVN) which overwrites a > more recent version of a file. > > How can this be prevented? Via hook-scripts, settings in > TortoiseSVN. I prefer doing SVN copy via right-click drag-n-drop in > TortoiseSVN than doing a cryptic Merge. I want to set a good > process to ensure that a team never overwrites new stuff.... > you could probably write a hook script for. But, if you instruct your devs to only do branching from the repository browser it will be done from head... unless they change repo browser to show an earlier revision... but that has to be done on purpose. Bob
