Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Wed, 23 Mar 2005 19:30:27 +0100, Bo Berglund
<bo.berglund at telia.com> wrote:
>On Wed, 23 Mar 2005 18:14:00 +0000, Tony Hoyle <tmh at nodomain.org>
>wrote:
>>Interesting... Tag isn't unique to a directory. What happens if you
>>update a directory with multiple branches in it?
>>
>I guess you mean when I *commit*...
>Well, normally the listing of the files on STDIN contains a number of
>files, then the Tag: line then new files and so on for each different
>branch tag they belong to.
>I will try to verify this on my 2.0.41 "production" server ASAP.
>
Now I have done this test, I created two different branches on two
files and then I modified these and a third one and committed them all
at once. This is what I see in the CVSMailer logfile on the 2.0.41a
server (Parameter line is wrapped by newsreader):
Parameter 4:
ModuleXX ModuleXXdoc.txt,1.45,1.45.2.1 SecondFile.txt,1.10,1.10.2.1
ThirdFile.txt,1.8,1.9
StdIn read:
Update of /pc/ModuleXX
In directory antares:C:\\cvstemp\\cvs-serv3796
Modified Files:
Tag: Branch_Two
ModuleXXdoc.txt
Tag: Branch_One
SecondFile.txt
No tag
ThirdFile.txt
Log Message:
Committing files to different branches
As can be seen the files are listed by tag with the final non-tagged
file having the designator "No tag".
The listing in CVSMailer now looks like this:
ModuleXXdoc.txt 1.45 1.45.2.1 Branch_Two Diff 1.45<=>1.45.2.1
SecondFile.txt 1.10 1.10.2.1 Branch_One Diff 1.10<=>1.10.2.1
ThirdFile.txt 1.8 1.9 Diff 1.8<=>1.9
I would very much like to have this behaviour back....
/Bo
(Bo Berglund, developer in Sweden)