Re: Merge to branch

2004-07-05 Thread news
Hello,

"Jim.Hyslop" <[EMAIL PROTECTED]> a écrit dans le message de
news:[EMAIL PROTECTED]
> Fixing this will be quite simple. For simplicity, I will assume that there
...

Thank you very much for this method. I didn't know it was possible to merge
2 versions in the same branch. I have to read some docs to be more familiar
with cvs (wincvs don't help, the help is a shame).

Cordialement.

Jean


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs


Re: Merge to branch

2004-07-05 Thread news
Hello,

"Rohan Nandode" <[EMAIL PROTECTED]> a écrit dans le message de
news:[EMAIL PROTECTED]
> If both main trunk and branch R18 are in sync till now, then you can
> merge the changes with following with branch as working copy.
>
> cvs update -j HEAD -j R18 

Thank you very much. It was the main trunk name (HEAD) I didn't know !
It worked.

Jean


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs


RE: Merge to branch

2004-07-05 Thread Jim.Hyslop
news wrote:
> I have a "main trunk" and a branch "R18". Some changes (on 3 
> files) have been made by programmer on the main trunk but 
> they should have been done in the R18 branch. I'd like the 
> changes made on the three files to be merged (or just copied) 
> to the R18 branch. Of course, the R18 branch should continue 
> to "live" but with the changes (I hope my english is good enougth...).
First of all, your english was more than sufficient to communicate your
problem.

Fixing this will be quite simple. For simplicity, I will assume that there
exist tags 'original' and 'incorrect', which refer to the trunk revisions
immediately prior to the check in, and immediately after the check in. For
example, if the developer had revision 1.2 checked out, modified it, and
checked it in to become rev 1.3 then 'original' would be 1.2, and
'incorrect' would be 1.3.

Since there are only three files involved, you could probably simply use the
numeric revision instead of applying tags.

On the trunk:

cvs up -j incorrect -j original file1 file2 file3
#fix up any conflicts#
cvs di file1 file2 file3
#examine the diff to ensure it looks reasonable#
cvs ci -m "Backing out changes incorrectly checked into the trunk" file1
file2 file3

On the branch:
cvs update -r R18
cvs up -j original -j incorrect file1 file2 file3
#fix up any conflicts#
cvs di file1 file2 file3
#examine the diff to ensure it looks reasonable#
cvs ci file1 file2 file3

Note that the order of the -j parameters is different between the two
commands. The first one does a "negative delta" to back out the changes on
the trunk. The second one does a "positive delta" to apply the changes to
the branch.

-- 
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. (http://www.leitch.com)
Columnist, C/C++ Users Journal (http://www.cuj.com/experts)



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs


Re: Merge to branch

2004-07-05 Thread Rohan Nandode
If both main trunk and branch R18 are in sync till now, then you can 
merge the changes with following with branch as working copy.

cvs update -j HEAD -j R18 
This also assumes that there are no commits to main trunk after your 
required changes. otherwise they will also be merged into the branch.

HTH
Rohan
news wrote:
Hello,
I have a "main trunk" and a branch "R18". Some changes (on 3 files) have
been made by programmer on the main trunk but they should have been done in
the R18 branch. I'd like the changes made on the three files to be merged
(or just copied) to the R18 branch. Of course, the R18 branch should
continue to "live" but with the changes (I hope my english is good
enougth...).
Thanks.
Jean
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs