Re: Branches and Dates
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 coexist -- in most cases, the existing code already does the right thing if you just remove the check. And given that it's an expansion of functionality, is there a problem with implementing it in the next version and then allowing other development teams to add it as they go? Probably not. Note, however, that it's a lot more work than just updating the code -- you need to update the documentation as well. -Larry Jones Why can't I ever build character in a Miami condo or a casino somewhere? -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Branches and Dates
I thought I understood this, but the evidence is against me ... 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 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 mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Branches and Dates
[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 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. You need to specify both the branch and the date. Unfortunately, not all CVS subcommands allow both -D and -r at the same time, but I believe that update is one that does, despite what the documentation may say. -Larry Jones Aw Mom, you act like I'm not even wearing a bungee cord! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Branches and Dates
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. a thing that could be fixed simply if someone were motivated c. a thing that could be fixed, but only with difficulty d. a thing that should be fixed, but cannot be, due to insurmountable internal problems or even different situations for the different subcommands. Please don't take this as criticism, Larry; that's not my intent! I'm merely trying to draw you out on the reasons. It'd be good to have that bit of your expertise on the record, in case someone tripping across this thread in the archives decides it's a project worth taking on :-) -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / Just Say No to the faceless cannonfodder stereotype. - http://www.ainurin.net/ (an Orc site) ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Branches and Dates
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 exactly how to best provide the capability. Some places in CVS allow you to specify a branch and a date in a single package, like update -j's branch:date syntax. Other places, like update, allow specifying -r and -D at the same time. Still other places, most notably diff, allow -r and -D at the same time, but interpret them as specifying two different revisions rather than jointly specifying a single revision. Trying to unify all that is a daunting task, particulary when you try to ensure that the result will be upward compatible (for all of clients, servers, and users). -Larry Jones That's one of the remarkable things about life. It's never so bad that it can't get worse. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Branches and Dates
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? Existing inconsistency coupled with profound indecision over exactly how to best provide the capability. Some places in CVS allow you to specify a branch and a date in a single package, like update -j's branch:date syntax. Other places, like update, allow specifying -r and -D at the same time. Still other places, most notably diff, allow -r and -D at the same time, but interpret them as specifying two different revisions rather than jointly specifying a single revision. Trying to unify all that is a daunting task, particulary when you try to ensure that the result will be upward compatible (for all of clients, servers, and users). Thank you for clarifying that. 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? And given that it's an expansion of functionality, is there a problem with implementing it in the next version and then allowing other development teams to add it as they go? Jenn V. -- Do you ever wonder if there's a whole section of geek culture you miss out on by being a geek? - Dancer. [EMAIL PROTECTED] http://anthill.echidna.id.au/~jenn/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
