[ On , April 1, 2002 at 16:16:21 (-0800), msenin wrote: ] Assuming you've tagged your release (a sadly mistaken assumption it seems) it's a trivial task to take the output of a command such as the fo
No, it doesn't delete it, but it does hide the old stuff (which is just as bad). Once the remove-add sequence is done, there is no reliable method to track down the original location, and under some
NO! One wants to be able to query based on this; more importantly, CVS itself needs to be able to do so to implement merge-tracking. The RCS file format is extensible; this shouldn't be a problem. I
The extension to the RCS format (ie. the data-storage layer) should be a general one. It should provide for storing an arbitrary set of named attributes (ie. key/value pairs) per revision. There shou
sandeepk1611 wrote, On 02/16/2011 05:26 PM: Easy. Same answer as I gave you last time when you wanted to search for substrings. :) By default cvs2cl lists its information by "change set", where "chan
That is the only way to change a log message. The file name is the one whose's log message you want to change: If you need to change the message in multiple files, you will probably have to use multi
I propose to use commit-time triggers by "cvs add -c" time instead of special add-to-repository-time triggers. Don't you wish to even try to understand the suggestion? The suggestion is: invoke *the
In my design the triggers are the same, so there is no such problem. Either the file is OK for repository or not, -- simple and clear. The less problems, -- the better. In your design there is "OK fo
Yes, but it was not the sense of my question. First of all, why? Is there a specific reason you want to rewrite history? I'd be concerned about what would happen if you changed the timestamps such th
There is no risk that cvs will get something confused. (The same may not be true for yourself.) There is no risk of cvs getting confused by creating a new branch from a version tag of any kind. Nah,
Agreed. :-) Yes, but diff is not diff3. diff is used for the delta format. diff3 is used by rcsmerge, not for fundamental version deltas. True, but examiniation of the rcs sources (or cvs sources) ca
My apologies for such a long message... it's a bit of a complex issue. Delete now if you're not interested :-) You've really got a loophole in your config file. cvs_acls is behaving as documented, al
More or less shooting from the hip here, since I haven't checked the code: a more sophisticated "is ambiguous" test might solve this. What does "ambiguous" really mean here? I think it should mean, "
Thanks for the detailed reply! Before this sample script, I actually thought that your idea was bad because every type of shell or operating system has its own way of redirecting the standard error -
Shlomo, If the "CVS internals" change for CVS/Root and CVS/Repository many people would be changing scripts. The global "-t" tag suggestion could be used. You are correct that the output goes to STDE
There are two separate problems here. The mysterious clobbering of changes is *not* responsible for what you saw when you tried to revert; the latter is expected behaviour. More information is called
Hi! Please let me know if there's a more appropriate mailing list. I have rebuilt cvs on my system under Cygwin, it wasn't hanging before. The last line I got after I ussued: "$ cvs update" was: cvs
why? why? why can't "cvs mv" just rename the *,v file? let me repeat: why can't "cvs mv" just rename the *,v file? why? I am not saying I will be doing "cvs mv" twice a day. I have felt the need for
[ On Friday, July 13, 2001 at 09:25:58 (-0500), Thornley, David wrote: ] Well, that might just be because you can't do that. I.e. you can't still have your cake and have eaten it too. Well, what is t