Jenn Vesperman writes:
Hrm. Given that some places (such as diff) need to be able to specify -r
and -D to mean two distinct revisions, would the branch:date syntax be
the most effective answer?
Probably. Unfortunately, it's more complicated to implement than just
allowing -r and -D to
with the branches collapsed.
For example, a file that existed only on the trunk mysteriously
appears in the branch if I use a date after the time it was added
to the trunk.
So what are the interactions between branches and dates?
#!/mjh
___
Info-cvs
[EMAIL PROTECTED] writes:
We have a situation where we need to see the state of a branch
at a point of time in the past. Problem is that if I checkout
the branch and then update ... -D date ... what I appear to get
is the state of the module at that date with the branches collapsed.
For
On Tue, Nov 19, 2002 at 10:16:47AM -0500, Larry Jones wrote:
You need to specify both the branch and the date. Unfortunately, not
all CVS subcommands allow both -D and -r at the same time [...]
Why not? I could see the reason being any of:
a. because they don't always make sense together
b.
Eric Siegerman writes:
On Tue, Nov 19, 2002 at 10:16:47AM -0500, Larry Jones wrote:
You need to specify both the branch and the date. Unfortunately, not
all CVS subcommands allow both -D and -r at the same time [...]
Why not?
Existing inconsistency coupled with profound indecision over
On Wed, 2002-11-20 at 10:06, Larry Jones wrote:
Eric Siegerman writes:
On Tue, Nov 19, 2002 at 10:16:47AM -0500, Larry Jones wrote:
You need to specify both the branch and the date. Unfortunately, not
all CVS subcommands allow both -D and -r at the same time [...]
Why not?
