On Saturday, February 19, 2000 6:32 AM, |}avid (opeland
[SMTP:[EMAIL PROTECTED]] wrote:
> Not to continue to harp, but:
>
> > No, you're not exactly right and what you're missing is perhaps a
> > critical facet that will help your understanding of this issue. "We"
> > (i.e. CVS) define tagging to mean which revisions of which files are to
> > be grouped together (perhaps for a release, or to mark a milestone,
> > etc.). I.e. the two go together: revisions + files.
> YES. I consider the removal of a file as a new revision of that file.
So does
> CVS. I simply want it to apply to concept of tagging, stat, and log to
the
> head revision of removed files just as it does to non-removed files. In
other
> words, removing a file is NOT a special case.
>
> As explained in my previous email, removing the tag does not work and I
> actually DO want to tag the removed version. This allows me to use CVS
to
> support our workflow and development process.
>
> We are NOT doing multiple lines of development, but enacting a process
WORKFLOW
> which says that files are in a different state at different times.
Whether or
> not the file is present or not doesn't (and shouldn't) matter.
>
If a file is removed how can it be in any state? If I understand you
correctly, you want to preverve the state of the files and are using the
tag for this. Have you looked at the state parameter for this? Then you
can have a single tag (e.g. release-1-2) and change the state to indicate
where the file(s) are. This is discussed in Cederqvist.
> (To recap, I have a moving tag that I use to indicate which revision of a
file
> is in which state of workflow). So, if have dev/stage/live tags, and the
dead
> revision is tagged as dev and as stage, but the previous (non-dead)
revision is
> tagged as live, that is the state where the client is approving a change
that
> involves REMOVAL of that file.
>
> If I had removed the tags, as you suggest, the file would be removed from
live,
> and this does not support our process.
>
Now I'm confused. You say that you want to remove the file (presumably so
that it is no longer a current 'live' file) and then say that if you remove
the tag "the file would be removed from live, and this does not support our
process". So what do you want to do with the removed file. You don't want
it to be shown in your HTML tree, but you don't want it removed.
> > > I find it hard to believe that the
> > > implementors INTENDED to have cvs commits not affect removed files.
> >
> > Now I'm really confused. A moment ago you were talking about tags.
Now
> > you you say "commits".
>
> I meant to say "cvs commands". My bad.
>
> > Actually if there is a tag then yes the removed file might be checked
> > out or exported at the wrong time. You definitely do not want to ever
> > tag "dead" revisions -- doing so puts the repository into an undefined
> > state and no guarantees can be made about what might happen as a res
ult.
> Not that I've seen. It seems to work exactly as I want it to. It's just
that
> to tag the dead revision, I have to run a different command than I do to
tag a
> non-dead revision. This is inconsistent and I see no need for it.
>
> > I think your understanding of the temporal structure of the repository
> > is not quite up to speed yet. Once/if you understand how CVS works
across
> > time perhaps you'll understand why "dead" revisions can never be
tagged.
>
> I'm not sure why you insist that dead revisions "cannot" be tagged and
that
> doing so will put the repository in an "unstable" state. I have
empiricly seen
> that this is not so.
CVS uses the Attic to retrieve tags from previous (historical) versions.
The head of the main trunk is only the files in the main directory. The
only time you will work on files in the Attic is when you extract a
historical tag, or you are working on a branch and create a file which only
exists on the branch (in this case the file is kept in the Attic and dead
on the trunk). Dead revisions contain tags which were created before the
file was labelled as dead, in order to allow the recreation of a previous
tag of the directory. Any tags you place in the main directory and
manually on a dead revision will cause the files in the main directory AND
the Attic to be delivered to you when you do a 'cvs co -r live'. Is this
what you want or do you only want the files in the main directory?
***************************************************************
Chris Cameron Open Telecommunications NZ Ltd
Software Development Team Leader
[EMAIL PROTECTED] P.O.Box 10-388
+64 4 495 8403 (DDI) The Terrace
fax: +64 4 495 8419 Wellington
cell: +64 21 650 680 New Zealand
Life, don't talk to me about life ....(Marvin - HHGTTG)
