I can see a reason, but in a slightly different context
cvs co -d mod-tag1 -r tag1 mod
cvs co -d mod-tag2 -r tag2 mod
vi mod-tag2/file1
vi mod-tag1/file1
cvs ci -m "Fixing serious bug in all branches" mod-tag1 mod-tag2
ciao,
Federico Carminati
==============================================================================
|| Federico Carminati || Tel.: +41.22.767.4959 ||
|| CERN-EP || Fax.: +41.22.767.9075 ||
|| 1211 Geneva 23 || ||
|| Switzerland || ||
==============================================================================
On Wed, 12 Jul 2000, Stephen Rasku wrote:
> Pavel Roskin wrote:
>
> >But strictly speaking you cannot check into many branches
> >"simultaneously". You need at least two checkin commands to do it.
> >
>
> Actually, you can check into multiple branches at the same time. Just
> not the same file at the same time. For example, given the following
> module:
>
> module/
> file1.c
> file2.c
> file3.c
>
>
> If you check out the module and then perform the following.
>
> 1. Modify file1.c
> 2. cvs update -r tag1 file1.c
> 3. Modify file2.c
> 4. cvs update -r tag2 file2.c
> 5. cvs ci (from inside module)
>
> file1.c will be committed against tag1 and file2.c will be committed
> against tag2. I have done this by accident several times but have
> always caught it because the editting window will list which files are
> being committed against which tags. This usually happens to me when I
> make a quick fix to a sub-module certain branch and don't change the
> branch back. My original question was whether there would ever be a
> reason to do this on purpose rather than by accident.
>
> --
> Stephen Rasku E-mail: [EMAIL PROTECTED]
> Senior Software Engineer Phone: (604) 872-6676
> TGI Technologies Web: http://www.tgivan.com/
>
>
