On Friday, February 18, "|}avid (opeland" wrote: > >(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. I think you should look into branches, not just tags. --Toby.
- Why does CVS treat removed files so specially? |}avid (opeland
- Re: Why does CVS treat removed files so specially? Greg A. Woods
- Re: Why does CVS treat removed files so specia... |}avid (opeland
- Re: Why does CVS treat removed files so sp... Greg A. Woods
- RE: Why does CVS treat removed files so specially? Chris Cameron
- RE: Why does CVS treat removed files so specially? Chris Cameron
- Re: Why does CVS treat removed files so specially? David L. Martin
- Re: Why does CVS treat removed files so specia... |}avid (opeland
- Re: Why does CVS treat removed files so sp... Greg A. Woods
- Re: Why does CVS treat removed files s... |}avid (opeland
- Re: Why does CVS treat removed fi... Tobias Weingartner
- Re: Why does CVS treat removed fi... Greg A. Woods
- Re: Why does CVS treat removed fi... Steve Greenland
- RE: Why does CVS treat removed files so specially? Chris Cameron
- Re: Why does CVS treat removed files so specia... |}avid (opeland
- RE: Why does CVS treat removed files so specially? dbockenf
- RE: Why does CVS treat removed files so specially? Chris Cameron
- RE: Why does CVS treat removed files so specially? Chris Cameron
- Re: Why does CVS treat removed files so specia... |}avid (opeland
