All, I use RCS via Emacs and really like what RCS does for me. However, is there a way to add a keyword to RCS? What I want to do is to be able to add a program description to my RCS files so that it
Works fine thanks - with ": " after "Log", of course. Not necessary. CVS will insert the colon. Actually, Log is one keyword that really is more trouble than it's worth, for several reasons. First, i
I've since read that \040 is used for spaces to keep the keyword string "well formed" for the benefit of keyword search tools. It appears that dollar signs will also be replaced. However, I don't nee
Yes, it is routine. You can even use RCS and CVS at the same time on the same project, they will mostly ignore one another. I maintain my system files through RCS all the time. What I do is create a
Tags can be used as a STATE substitute, however the nice thing about STATEs is that it's much easier to revert to a last known good state, for example. With tags, however, once you've moved your tag,
[ On Friday, July 27, 2001 at 13:48:25 (-0700), Josh Baudhuin wrote: ] RCS "states" are far far less useful in CVS than they can be in RCS. That's because CVS already uses the RCS state for "magic" i
D'uh woops. It occurs to me that the -T was not what was keeping us from having to recompile--it was because our wrapper script reset the committed (ci'd) file to the timestamp it had before the ci o
There are a couple of things in RCS that CVS doesn't have any longer (i.e., since cvs-1.10) that I find a little odd and vexing. First off, I'd expect that the update and commit command would have co
Hi all If you have two files a.txt (two lines) : -- $Id: $ $Name: $ -- b.txt (one line) -- $Name: $ -- Add those to CVS - check out the module and run "cvs tag TAG1" Then $ echo "hi there" >> a.txt $
[ On Monday, July 9, 2001 at 00:01:01 (-0400), Eric Siegerman wrote: ] Well, with CVS the meaning of "frozen" file is quite a bit different. In the most basic sense what I'm saying is that "-kv" shou
My monthly resend of this script. I guess I'll include the script directly this time in the hopes that maybe people don't like attachments and that's the reason I still haven't gotten a response from
I come again, implement `$DateZone: (ZONENAME)$'. In this implementation, a writer specifies the timezone. Then, the behavior is a place-independent. A problem of this implementation is the literal Z
I realize that the follow-up I sent a week or two ago didn't made it to the list :/ Please find here some comments to your reply, then my original follow-up :) Sounds good :) I had in mind to sign wh
See my reply to your 'Inaccurate documentation re "cvs tag"'. commit does an update to keep things consistent between your sandbox and the repo when it gets done. BTW I think you should stop thinking
Rehul, I've removed bug-cvs from the list of recipients since I do not think it is related to this discussion. I've forwarded your comments on the patch to our development manager, but I would sugges
Hello Arthur : See response below: Arthur Barrett wrote: Rahul and Patrick, T In particular your original patch was not suitable for inclusion in CVSNT (or probably for cvs 1.12) as it has a hardcode
Mmm, yes. If it stripped out the values at commit time, and just stored the keywords, all these *#(! merge conflicts would go away. Why is this a problem? I very much prefer it. Suppose, using SCCS o
I originally posted this to the newsgroup fa.info-cvs, but it appears to be oneway. Pardon if this is a repost. BRIEF == I invite discussion of a patch that I have made to CVS, but not yet released,
Using GNU diffutils, the 'diff -x CVS -r dir1 dir2' with and optional -c for contex or -u for unified style diffs is how I typically do this kind of comparison. The '-x CVS' option tells GNU diff to