Hi Paola, Hmmm... it seems you are correct. Only isalpha() characters are allowed in RCSkeywords and that is inherited by the LocalKeyword directive. You can see it for yourself in expand_keywords i
Jason, As previously pointed out CVSNT is different to CVS. CVSNT runson Unix, Linux, Windows etc etc and is GNU Open Source (free). You can download a linux RPM or the sources from here: http://www.
The cvshome.org CVS versions do not support the CVSNT -ku Unicode extension at this time. If someone wishes to provde a patch with test cases to port that CVSNT feature to CVS, please feel free to su
I'm running cvs 2.0.2 (via WinCVS 1.3) on the client side, and the linux server has version 1.11.5 running. I'm trying to add a unicode file using the -ku option, which my wincvs client seems to thin
[I corrected the ISO 8691 format in the above quote.] It's only a matter of replacing the slashes (`/') with dashes (`-'), so that change should be pretty straightforward too. Got me here. I tend to
Hello, Sorry for coming to this discussion this late, but IMHO, using the "RCS way" (ident with $Id$ in the source code *and* the binary) seems to me to be the best solution for what Katherine needs.
Or use the GNU diff -I option to ignore those lines in the first place. -Larry Jones In a minute, you and I are going to settle this out of doors. -- Calvin
First, thank you for your reply. :-) The parsing of the RCS files should be trivial enough, the format does not look too complicated to me. Of course, I haven't yet read the rcsfile-manpage thoroughl
[ On , April 8, 2002 at 09:13:01 (-0700), Hamish Allan wrote: ] 'cvs import' does not "work" from within a working directory (aka sandbox) -- i.e. it does not do anything special. Or rather it only w
[ On Thursday, March 21, 2002 at 09:46:06 (-0800), Noel Yap wrote: ] That's certainly a good suggestion that anyone making use of this hack should be very careful to follow. Also check to make sure '
I think that the server "writes back" the files to the client. Isn't this the way keywords are expanded on the client side once the checkin is through? Shubho --Original Message-- From: address@hidde
Received: from fencepost.gnu.org (address@hidden [199.232.76.164]) by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA04285 for <address@hidden>; Mon, 12 Feb 2001 20:17:34 +0900 Re
It has been the practice in shops where I work to archive a program's docs in the repository and to apply appropriate version tags to these docs. IMO it is a good practice, and I plan to continue to
And just how is this done? Do you use artifacts of the programming language to somehow format the marker into something that is not detectable by CVS? What if the language provides no way to do this
Hi, I have a minor problem with the Keyword Substitution in CVS / RCS. In my Source codes there are the Keywords. CVS/RCS is substituting these correctly, but in the wrong format. This is valid for t
"Proposal to improve CVS binary file implementation" would probably have been a better title. The larger issue of devising a true "fix" for binary file implementation is a good topic for discussion,
Michael, http://www.cvsnt.org/manual/html/Substitution-modes.html The keywords themselves can be used defined - so this list is arbitrary. http://www.cvsnt.org/manual/html/Keyword-substitution.html A
It's -kv, not '-ko'. '-kv' removes the keyword (and the bracketing $$) and leaves only the value. Your files will end up looking like this: * Since $Revision: $: still working * Since 1.24: ladidda b
I don't think so. The problem is, the RCSkeywords are not expanded until you check the file out. By that point, you've lost the context of when the keyword was added. Could some combination of 'cvs