Hi all - I am talking to some folks (both in house and at another company) about $Log$ functionality, and I have some questions that I was hoping someone could answer quickly: - Is there a more detai
This is to continue the discussion of the thread with the same subject that started on Dec 7, 2004. The original discussion appeared to focus on the expansion of the $Log$ keyword both in the file an
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
Hello, If $Log$ appears anywhere in a script it would be expanded while CVS checkin. Does anyone got in any troubles with this scenario yet? Though chances are less as we always enlcose the variable
Try using the 'export' command. The idea, I think, is that with a checkout you might be temped to modify the code thus invalidating the Name keyword, whereas with an export it is explicit that you sh
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
Rahul and Patrick, Thanks for submitting the patch. Our development manager has had a look at it and found that it is unsuitable for inclusion in CVSNT, however a simpler solution has been found and
But be warned: although changing it will cause $Log$ entries to be added for *future* commits, it will *not* magically go back and insert entries for commits were done while the file was set to -kb.
Educate the programmer; or disable keyword substitution, perhaps only for that file. Those are the only two choices. -- Patient: Doctor, it hurts when I do this. Doctor: Then, don't do it!
Hi there ! I would like to use the $Name$ Keyword in my java source. To do this, I added the line: public final static String cvsRelease = new String("$Name$"); to my source. Then, I tagged it "prere
Hello! I found the post below in the info-cvs archives from April of 2001. Can anyone tell me if this issue has been fixed? I have just run into this problem (using a somewhat backlevel version of cv
Windows does not distinguish between text and binary files. It does, however, use a different line ending than CVS' canonical line ending, which is the Unix line ending. If, however, these were boru
IF (and that's a big "if") you're lucky enough to be working on systems that do not differentiate between text and binary files (Unix and Linux, for example, do not; Windows does), then all you have
Hi to all, I have erroneously imported a lot of C source files with the -kb option. I realized this error only after a lot of modification on that files. Does somebody know how to change the option t
Hi there ! I would like to use the $Name$ Keyword in my java source. To do this, I added the line: public final static String cvsRelease = new String("$Name$"); to my source. Then, I tagged it "prer
I thought the attic files accounted for it, but I've just run a full "cvs log -rBRANCHNAME" on our tree, with a perl script to parse out the 'dead' files - and we still get something like 30-40 files
I tried "cvs log UserManagerTest.java > userManagerLog.log" and getting "cvs [log aborted]: there is no version here; do 'cvs checkout' first" as the response. If I use cvs log > logfile.log, the log
Yes, this is one of the lame things about cvs log. (Hmm... What happens if you turn off the headers?) I wrote a wrapper script cvslog.pl which eliminates the non-relevant junk, that is, the files for