[cvsnt] Re: Build 1921 still changes the file branch tags on update!

[Bo Berglund]

I am using this a lot at work where we use 2.0.41 on the server and 
2.0.41 as clients.

Basically the idea is to put one or two files in a folder that is 
checked out to a branch into a separate branch (private) or on to
the TRUNK. The reason may be that these files are either used only
for local configuration or they should not be changed on the branch
for some other reason. We have language files that are never branched
for example. They belong on TRUNK.
So I update them to a different branch or reset the tag.

Then when I update the sandbox to retrieve changes from other developers
I don't expect these files to suddenly revert back to the folder branch.
They should keep the tag they are set to carry, either a branch tag, no
tag or a sticky tag. The update should evaluate the situation with 
reference to the tag and act accordingly.

But this is exactly what happens and I noted it first when testing the
behaviour of release 2.5.01 (or possibly one of the RC:s).

No good....

Why should a tag that is set in the Entries file be changed by an update?
Seems contradictory to what the tags are meant for.

/Bo

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Tony Hoyle
Sent: den 30 mars 2005 14:31
To: cvsnt at cvsnt.org
Subject: [cvsnt] Re: Build 1921 still changes the file branch tags on
update!


Bo Berglund wrote:
> Situation with 2.5.01.1921:
> -Sandbox checked out to a branch tag (Branch1).
> -One file updated with "reset sticky" (HEAD)
> -Two files updated to two different branches (Branch2, Branch3)
> 
> When running an update on the sandbox all files revert back to the
> Branch1 tag!

Has this ever worked?  I haven't been near that code since last year.

Tony
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt