Hello,
* On Wed, May 25, 2005 at 09:52:59AM -0400 [EMAIL PROTECTED] wrote:
> What is the option/syntax to ignore keywords during an update?
>
> > cvs up -k???
cvs up -kk
(see the double "k")
Regards,
Spiro.
--
Spiro R. Trikaliotis
What is the option/syntax to ignore keywords during an update?
> cvs up -k???
--
Chris T Fouts
Infineon Technologies Corp
3000 CentreGreen Way
Cary, NC 27513
Phone: (919)677-3016
Fax: (919)678-1929
Email: [EMAIL PROTEC
Glenn Franxman wrote:
Thanks Jim!
It turns out that the $Name$ tag is treated special.It gets
expanded when the command is export, but not for checkout or update.
Hmm, a little experimentation shows me that that is not correct, at
least for 'cvs update':
sahp6613% more test4.dat
# $Name
Thanks Jim!
I searched through the archives and found a lot of other posts
covering the same problem.I did eventually find the needle in the
haystack, so I thought I'd post it here to improve the
problem:solution ratio.
It turns out that the $Name$ tag is treated special.It gets
Glenn Franxman wrote:
> Please excuse the n00b question. I'd like to have some sort of text
> inserted into my source code upon checkout, much like the $id: $ and
> other tags, but would contain the branch id or latest tag.
$Name$ seems to come the closest:
https://www.cvshome.org/docs/manual/cvs
Please excuse the n00b question. I'd like to have some sort of text
inserted into my source code upon checkout, much like the $id: $ and
other tags, but would contain the branch id or latest tag.
Is there any such provision in cvs? Is there a reason that there
wouldn't be or shouldn't be?
_
Hello,
* On Thu, Oct 21, 2004 at 01:25:28AM -0700 Dizel wrote:
> /* $magic_keyword: file library.c,v1.22 2004/08/21 ...$ */
> Is any keyword like this $magic_keyword$ in CVS?
Did you try $Id$? CVS understands all RCS keywords.
Regards,
Spiro.
--
Spiro R. Trikalioti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dizel <[EMAIL PROTECTED]> writes:
> In my project I use two separate directories: the main program source,
> and the library source, used by main program to build.
> The main program and library commit to CVS repository independently.
> There is a so
Hello!
In my project I use two separate directories: the main program source,
and the library source, used by main program to build.
The main program and library commit to CVS repository independently.
There is a some problem: Then I checkout main program, i don't know
the version of library it's
Title: Blank
I have a bulk merging proces (also binary files)
Import a vendor version wich differs only for a few files from the
trunc.
Most files are like the trunc except the keywords expansions.
The problem is that the import notices conflicts, cause by only and only
the keywords
may be cvs status command is what you looking for.
-Rohan
Sjur Vestli wrote:
Dear All,
CVS does keyword subsitution ($Revision$, $State$, etc.). With the cvs "log"
command I can extract the complete "state" of a particular file, including
its current revision, state, etc. etc. in a rather verbose f
Dear All,
CVS does keyword subsitution ($Revision$, $State$, etc.). With the cvs "log"
command I can extract the complete "state" of a particular file, including
its current revision, state, etc. etc. in a rather verbose format.
Is there a simple way of doing a "log" (or whatever) so that I get a
Hi
We are moving our projects from Continuus to CVS.
I have one question. Before moving the files to CVS,
should we add the keywords like author, date,
logmessage etc to the files? Is it recommended?
Thanks for any advice.
Mala
__
Do you Yahoo!?
Yahoo! Mail
, etc.
cheers,
matt
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Hi all.
I just wondered if there's a way to define my own keywords. I guess this
is somewhat hardcoded into cvs, but what alternatives are there to for
example insert a standard copyright message into source files?
Thanks,
Fredrik
___
Inf
Nick Patavalis writes:
>
> Is this true? I thought that expansion occured as a part of the
> *export* (cvs checkout, cvs diff, cvs export, etc) operations.
Both are correct. The actual process of expanding keywords happens
during checkout, but committing a file containing keywords tr
Reading from the CVS (info) manual [keyword substitution / using
keywords]:
To include a keyword string you simply include the relevant text
string, such as `$Id$', inside the file, and commit the file. CVS
will automatically expand the string *as part of the commit
operation*.
Is
Thanks for your reply Larry.
Could you please just clarify a few queries for me? That would be great.
> cvs import -W "*.gif -k 'b'" -W "* -k 'o'"
1. Is it just '*' as opposed to '*.*'?
2. Do I need to use the wrappers every time I import this 3rd party
source?
I'm assuming I do need to.
h how easy it is depends on what platform you're on and how
the files are organized. Keywords are replaced on checkout/update, not
import, so you don't *have* to worry about B until later, although you
might want to.
If you're on a platform that doesn't distinguish between t
Hi,
Is it possible to import a third-party source containing:
1) Binary files (GIF images)
2) PHP source files containing $Id$ keyword
Without:
A) Corrupting the images
B) Replacing the $Id$ keyword with my local info
'cvs import -ko' maintains the keywords, but corrupts the images
&
> Weird. Are you *sure* the umask is 002?
Yep. I type umask at the shell (csh, Bash) and get "2".
> - People run "cvs ci" via a script that's messing with
> the umask
Verified that the binary is running.
> - commitinfo or other triggers (not sure if this could have
> an effect, b
On Tue, Oct 23, 2001 at 03:01:48PM -0700, Glew, Andy wrote:
> "cvs ci" seems to change the file permissions,
> removing group write, if keywords are expanded.
> It does not if no keywords are expanded.
> [...]
> Have set umask to 002, so that most operations
> make f
the file permissions,
removing group write, if keywords are expanded.
It does not if no keywords are expanded.
DETAIL:
Using cvs 1.10.8
on RedHat LINUX 2.2.16-3smp
(maybe should be upgraded, but I am
not root)
Working on a system where we want all files
to be owner read write and group read write
Folks,
Derek Price, the cvshome.org webmaster, suggested I mail these lists
with this suggestion. I'm not on the lists, so I'd appreciate cc's of
replies. Thanks.
Anyway;
Working on the FreeBSD documentation and website we currently embed
various CVS keywords around the text
[EMAIL PROTECTED] (Larry Jones) writes:
> No. CVS uses the "correct" line endings for the platform where it's
> running.
Not if the "platform" is a combination of different OSes and editors
used during different parts of the development process (which is the
case quite often these days).
(I've
Jordi Castells writes:
>
> I have the repository in a Linux machine to hold both linux and
> dos/windows projects, I have checkout a dos project (where files have
> ending line with CRLF) into my windows disk (mount under linux too),
> when I commit I found that the expansion of
hi all,
I have the repository in a Linux machine to hold both linux and
dos/windows projects, I have checkout a dos project (where files have
ending line with CRLF) into my windows disk (mount under linux too),
when I commit I found that the expansion of keywords ($log$) do not
include as ending
I was hoping to display a Tag value on an information screen in my programs
using the Keyword $Name$. This works for Tags put not for branch tags. Is
this actually true or am I again missing something?
___
Info-cvs mailing list
[EMAIL PROTECTED]
h
On Tue, Aug 08, 2000 at 13:07 -0400, Larry G. Irwin II wrote:
> I was wondering if anyone knew of a way to define your own
> keywords in CVS along with what values are substituted in for
> that custom keyword.
>
> If this has already been discussed, please direct me.
You might
I was wondering if anyone knew of a way to define your own keywords in
CVS along with what values are substituted in for that custom keyword.
If this has already been discussed, please direct me.
Thank you.
That is all
In article <[EMAIL PROTECTED]> you wrote:
> I started playing with cvs, but i am having problem related to how to
> substitute keywords in my source files!
>
> This is the header of a C source from the FreeBSD Operating System! Can
> some here explain how i can have
Hi folks!
I started playing with cvs, but i am having problem related to how to
substitute keywords in my source files!
This is the header of a C source from the FreeBSD Operating System! Can
some here explain how i can have this working with my sources!
(what is getting me crazy is how to
st by giving that parenthesized comment.
[EMAIL PROTECTED] on 03/17/2000 01:24:57 PM
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Re: CVS keywords and make
> > But, since I started using C++, I have been plagued
> > by long build times. (Yes, I've read Lakos.)
Can
[ On Friday, March 17, 2000 at 13:47:12 (-0500), Larry Jones wrote: ]
> Subject: Re: CVS keywords and make
>
> > > 2. Larry posted the most elegent solution ...
> >
> > Larry posted a most gross hack ...
>
> But it was an *elegant* gross hack! ;-)
Absol
> > > But, since I started using C++, I have been plagued
> > > by long build times. (Yes, I've read Lakos.)
>
> Can someone give me a URL for Lakos?
>
> Michael
John Lakos
Large Scale C++ Programming
http://cseng.aw.com/bookdetail.qry?ISBN=0-201-63362-0&ptype=0
That's just an URL in Addison-
> > 2. Larry posted the most elegent solution ...
>
> Larry posted a most gross hack ...
But it was an *elegant* gross hack! ;-)
-Larry Jones
I've got more brains than I know what to do with. -- Calvin
> > But, since I started using C++, I have been plagued
> > by long build times. (Yes, I've read Lakos.)
Can someone give me a URL for Lakos?
Michael
[ On Friday, March 17, 2000 at 08:11:15 (-0500), Noel L Yap wrote: ]
> Subject: Re: CVS keywords and make
>
> 2. Larry posted the most elegent solution for the problem at hand though it
> won't help in your situation.
Larry posted a most gross hack (make -t) as well as an expl
[EMAIL PROTECTED] on 2000.03.16 23:56:29
>[ On Thursday, March 16, 2000 at 14:57:34 (-0500), Noel L Yap wrote: ]
>> Subject: Re: CVS keywords and make
>>
>> [EMAIL PROTECTED] on 03/16/2000 01:05:28 PM
>> >Back-dating the file on commit (i.e. when the update i
On Thu, 16 Mar 2000, Andy Glew wrote:
> I'm in a quandary.
>
> I like using CVS/RCS keywords like $Header: $
>
> But, since I started using C++, I have been plagued
> by long build times. (Yes, I've read Lakos.)
>
> To the point where I am seriously consid
[ On Thursday, March 16, 2000 at 13:27:19 (-0600), Andy Glew wrote: ]
> Subject: Re: CVS keywords and make
>
> Unfortunately, CVS's defaults are a bit awkward.
I don't find that to be true, but then again I don't try to overload the
meaning of keyword flags and thus I d
[ On Thursday, March 16, 2000 at 14:57:34 (-0500), Noel L Yap wrote: ]
> Subject: Re: CVS keywords and make
>
> [EMAIL PROTECTED] on 03/16/2000 01:05:28 PM
> >Back-dating the file on commit (i.e. when the update is done to retrieve
> >the new keyword values) is definitely
Noel L Yap writes:
>
> [EMAIL PROTECTED] on 03/16/2000 01:05:28 PM
> >Back-dating the file on commit (i.e. when the update is done to retrieve
> >the new keyword values) is definitely not possible (i.e. is wrong) as a
> >general solution.
>
> Why do you say this? I don't see a problem so long a
> I think the best solution to your problem is to do ``make -t''
> immediately after the checkin (-t tells make to just touch the files
> that are out of date rather than remaking them). Detecting whether a
> file "really" needs to be remade or not is a very difficult problem that
> is essentiall
[EMAIL PROTECTED] on 03/16/2000 01:05:28 PM
>Back-dating the file on commit (i.e. when the update is done to retrieve
>the new keyword values) is definitely not possible (i.e. is wrong) as a
>general solution.
Why do you say this? I don't see a problem so long as the file is backdated to
the
Andy Glew writes:
>
> Once tests pass
> (4) check in the file
>
> The problem is that step (4) modifies the RCS/CVS keywords,
> even if nothing else in the file is modified. Leading to
>
> (5) Unnecessary remake of the file
> (and all files that depend on it)
>
timestamp of the
object file).
Noel
[EMAIL PROTECTED] on 03/16/2000 11:34:34 AM
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Re: CVS keywords and make
Laird: I think that your question is of general interest,
so I am replying to the mailing list.
(Woo
Neither Cygnus CodeFusion nor Microsoft VC++
seem to be smart enough to do this.
The only IDE that seems to be smart enough to do this
is IBM Visual Age, which keeps everything in a database.
But then, you don't need CVS.
> or stop using RCS keywords in your source files.
>
> You
[ On Thursday, March 16, 2000 at 10:14:44 (-0600), Andy Glew wrote: ]
> Subject: Re: CVS keywords and make
>
> Laird: I think that your question is of general interest,
> so I am replying to the mailing list.
>
> The problem is that step (4) modifies the RCS/CVS keywords,
>
t; if you just made a change, then isn't the file modified? And if the
> file is modified, then isn't a remake always necessary? How will
> stripping keywords solve this problem?
Here's how I work:
(1) checkout the file
(2) make change
(3) compile and test the file
Once te
n't a remake always necessary? How will
> stripping keywords solve this problem?
Here's how I work:
(1) checkout the file
(2) make change
(3) compile and test the file
Once tests pass
(4) check in the file
The problem is that step (4) modifies the RCS/CVS keywords,
even if nothing else
I'm in a quandary.
I like using CVS/RCS keywords like $Header: $
But, since I started using C++, I have been plagued
by long build times. (Yes, I've read Lakos.)
To the point where I am seriously considering
removing CVS keywords from my files,
or at least disabling them with -k
52 matches
Mail list logo
