[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Race condition merging branches
From: |
Alex Holst |
Subject: |
Re: Race condition merging branches |
Date: |
Mon, 27 Aug 2001 17:22:14 +0200 |
User-agent: |
Mutt/1.2.5i |
Quoting Carel Fellinger (address@hidden):
[..]
> but this obviously leaves out the stuff in branch_n, so I have
> to use the generic branch tag and switch command order:
>
> cvs update -j branch_n-1 -j branch
> cvs rtag -r branch branch_n
>
> but how can I be sure that in between those two cvs commands nobody
> be left out in the next iteration of branch merges were
This seems like another problem that should be solved by interacting with
humans rather than hoping a tool will do it for you. A process should be
defined that outlines who is allowed to merge branches and how they must
notify other committers..
--
I prefer the dark of the night, after midnight and before four-thirty,
when it's more bare, more hollow. http://a.area51.dk/