Hello
I'm new to implementing CVS, and have a question regarding the fundamentals
of the CVS repository.
Is it possible to add custom fields to the repository?
I want to attach some meta data (eg: description, synopsis etc) to files in
the repository, but the standard version I've installed
At 06:30 AM 6/18/2003, Patrick Kennedy wrote:
Is it possible to add custom fields to the repository?
No. But CVS is open source so you can extend it yourself if you are inclined.
I want to attach some meta data (eg: description, synopsis etc) to files in
the repository,
If you want to keep
Just wanted to say thanks, got the CVS Sever up and running finally, just started
testing it... Hopefully all will go well. Thanks again to all who helped me out.
-Kristopher G. Hollingsworth
_
Free email at www.Z6.com ( and
Dear cvs readers,
I've got this problem. I just download ans set up my new cvs server based
on the cvs-1.12.1 version.
Inside my repository (localized in /var/cvs_repositories/ort) I have set
the CVSROOT/passwd file with :
anonymous:
bobenrieth::cvs
strohl::cvs
where cvs is one of the
I've seen the subject of CVS allowing files to be removed from tagged
versions (as opposed to forcing you to create a branch to modify instead)
kicked around in a few other messages from a couple years ago. Does anyone
know if there has been an update on this lately? From what I can tell that
Can CVS use an input file in place of options for each individual file.
We have a list of files that makes up a recipe of what source code is
needed to make a product. I would like to use this file as a input to a
CVS command to do checkouts, tag, commit, etc.
Here is an example
Input file
On Wed, 18 Jun 2003, Mischke, MaryBeth wrote:
I've seen the subject of CVS allowing files to be removed from tagged
versions (as opposed to forcing you to create a branch to modify instead)
If you are talking about removing a file that has a sticky tag, no this
is not allowed. You get a
Hamid Ghassemi [EMAIL PROTECTED] writes:
Can CVS use an input file in place of options for each individual file.
No, cvs does not have such an interface.
-- Mark
We have a list of files that makes up a recipe of what source code is
needed to make a product. I would like to use
Maybe I'm missing something in the nuances of tags versus sticky tags. Here
is what I am doing.
I checkout using: cvs checkout -P -r D-1-0-0-0 test
Then mark a file to be removed by using: cvs remove test.cpp
Then commit and the D-1-0-0-0 tag is removed from test.cpp file. If I
checkout the
I have what I am hoping is an easy question
but I cannot find the answer anywhere online
or within any CVS doc that I have access to.
I am using a modules file entry to give me
a subset of directories contained within
another module. This works great when I
perform a checkout but, when it comes
I just reread the rcsfile man page and had the following question. This
question might be answered if I read the source code to cvs, but I
haven't yet.
Basically, why do you need have
branches{num}*;
under the delta node (grammar).
It seems to be redundant because the
num
that
On 18 Jun 2003, Ronald Petty wrote:
I just reread the rcsfile man page and had the following question. This
question might be answered if I read the source code to cvs, but I
haven't yet.
Basically, why do you need have
branches {num}*;
under the delta node (grammar).
It
But you can tell this information by just looking at num
ex.
1.2.2.1 (means it branched at 1.2), however if you look at 1.2 it says
branch 1.2.2.1 is a branch rooted at itself, which is the exact same
information.
It looks to me how you chose to write your programs to get the data.
For people
I am using version 1.11.5
I had some trouble when moving from 1.11
my server args in xinet.d/pserver were
-f --allow-root /blah -f --allow-root /blah/blah etc.
(note the spaces)
I kept getting unrecognized auth
I found that if I changed to my server args to
-f --allow-root=/blah -f
On 18 Jun 2003, Ronald Petty wrote:
But you can tell this information by just looking at num
ex.
1.2.2.1 (means it branched at 1.2), however if you look at 1.2 it says
branch 1.2.2.1 is a branch rooted at itself, which is the exact same
information.
I think that the RCS file format is
I agree, well unless someone tells me that the information is incorrect
then num is good enough for parsing in my book.
Thanks Kaz,
Ron
On Wed, 2003-06-18 at 16:19, Kaz Kylheku wrote:
On 18 Jun 2003, Ronald Petty wrote:
But you can tell this information by just looking at num
ex.
Don Butts writes:
I am using a modules file entry to give me
a subset of directories contained within
another module. This works great when I
perform a checkout but, when it comes
time to update that checkout I get all of
modules files, not just the ones specified
in the modules file.
Kaz Kylheku writes:
If you are talking about removing a file that has a sticky tag, no this
is not allowed. You get a message like: ``cannot remove file 'foo.c'
which has a numeric sticky tag of 1.1''.
That only happens if the sticky tag is numeric. If the sticky tag is
symbolic, then the
[EMAIL PROTECTED] writes:
where cvspserver contains :
args=--allow-root=/var/cvs_repositories/ort /var/cvs_repositories/den
You need to repeat the --allow-root=:
args=--allow-root=/var/cvs_repositories/ort
--allow-root=/var/cvs_repositories/den
if [ -n $args ]; then
exec
Mischke, MaryBeth writes:
I've seen the subject of CVS allowing files to be removed from tagged
versions (as opposed to forcing you to create a branch to modify instead)
kicked around in a few other messages from a couple years ago. Does anyone
know if there has been an update on this
mike walster writes:
I had some trouble when moving from 1.11
my server args in xinet.d/pserver were
-f --allow-root /blah -f --allow-root /blah/blah etc.
(note the spaces)
That has never been valid syntax, I can't imagine how it worked in 1.11
unless it was some kind of local
Ronald Petty writes:
1.2.2.1 (means it branched at 1.2), however if you look at 1.2 it says
branch 1.2.2.1 is a branch rooted at itself, which is the exact same
information.
As I'm sure I've explained to you before, what the branch node gives you
is the first revision on the branch. For
22 matches
Mail list logo
