On Wednesday 30 June 2010, Jan Lund wrote:
> 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) whic
EATLY appreciated! Changes can otherwise
get lost in production...
--- Den ons 2010-06-30 skrev Bob Archer :
Från: Bob Archer
Ämne: RE: out of date branches
Till: "Jan Lund" , "users@subversion.apache.org"
Datum: onsdag 30 juni 2010 17:55
> -Original Message-
>
e.c,
Revision, 1112)
(.)
Revision: 1151
Author: user1
Date: 07:38:28, den 30 juni 2010
Message:
>From /releases/old/
Replacing : /production/filename.c (Copy from path: /releases/old/filename.c,
Revision, 1146)
--- Den ons 2010-06-30 skrev Bert Huijben :
Från: Bert Huijben
Ämne: R
> -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 enforc
[mailto:janne_l...@yahoo.com]
Sent: woensdag 30 juni 2010 17:28
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
deve
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
