-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Larry
Larry Jones wrote:
Diego Sevilla Ruiz writes:
I have three directories into my repository (into
somewhere/cvsroot):
dir1
dir2
dir3
When I do a "cvs update" in the parent directory, I have those
three
Hi, all
I experienced the following problem:
I created a directory once upon a time in my source tree which wasn't under CVS control
at that time. Let's call this tree 'tree1'. Later on I created a branch and put that
directory under CVS control in that branch. When I try to do a 'cvs log' in
Hi,
Is there a way of sorting tags according to the revisions that they tag?
Specifically I would like to find the latest tag that was put on a given
branch. (Suppose that all files in a CVS project are always tagged
together, so in general I could take the output of "cvs log" for any single
Hello,
I need to set up a central repository for 6 remote sites that will
have both Unix NT clients. Reading through the sparse documentation
on remote repositories and setting up CVS client / server, I'm
unclear whether this utility will meet my requirements or if it's
more
suited to
Diego Sevilla Ruiz writes [quoting me]:
If not, how did you
checkout dir1, dir2, and dir3?
Yes.
"Yes" is not an appropriate answer to "how".
-Larry Jones
My dreams are getting way too literal. -- Calvin
Martin Apel writes:
When I try to do a 'cvs log' in tree1 now,
CVS complains:
cvs log: in directory acis:
cvs [log aborted]: there is no version here; do 'cvs checkout' first
The directory is even listed in .cvsignore in the parent directory in tree1.
It seems that CVS doesn't
Hi,
I have a problem regarding the setup of
ssh tunneling for cvs ("Again!", might some people shout...).
I have to use this solution since our developers are using
a commercial solution with a cvs interface. Unfortunately this
interface supports only :server: and :pserver: methods,
and the
On Thu, 27 Jul 2000, Larry Jones wrote:
Martin Apel writes:
When I try to do a 'cvs log' in tree1 now,
CVS complains:
cvs log: in directory acis:
cvs [log aborted]: there is no version here; do 'cvs checkout' first
The directory is even listed in .cvsignore in the parent
Martin Apel writes:
In the CVS/Entries file for tree1 there is no entry 'acis' !
This was the first thing I tried to do.
Are there any lines in CVS/Entries (or CVS/Entries.Log) that start with
"D"? If so, there must be one for acis; if not, add a line to the
bottom of the file containing
[EMAIL PROTECTED] writes:
I need to set up a central repository for 6 remote sites that will
have both Unix NT clients. Reading through the sparse documentation
on remote repositories and setting up CVS client / server, I'm
unclear whether this utility will meet my requirements or if
Please help.
i importet a new CVS root using (CVRSOOT=/usr/local/cvsroot):
`cvs import my_project1 v0id start`
Everything is fine and i can "use" CVS. My problem now is that i want
to remove my_project1 from the CVSROOT. I know that i could do `rm -r
/usr/local/cvsroot/my_project` but thats not
We have people working on multiple AIX nodes and NT all using the same
repository. We are working all at the same site, but as long as you can ping
the repository server, the following (should) work fine (If you have port
blocking routers/firewalls then extra firewalls configurations will be
From: "Reinstein, Shlomo" [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" [EMAIL PROTECTED]
Subject: Sorting tags
Date: Thu, 27 Jul 2000 06:14:11 -0700
X-Mailing-List: [EMAIL PROTECTED] archive/latest/19057
Hi,
Is there a way of sorting tags according to the revisions that
they tag?
Specifically
Our cvs server computer was offline for a while, now that it is back
up, when I try to check out the source code I get the following error:
cvs co src
/bin/cvs
cvs server: existing repository /usr/local/cvs/root does not match
/usr/local/cvs/root/src
cvs server: ignoring module src
Any
Eric Sommerlade wrote:
I was searching for this CVSPORT variable desperately, yet
unsuccessful.
Does it exist (in cvs =1.10.8), or is there another way to
specify the client side port number to connect to?
My apologies. Someone else posted something similar, I remembered
reading about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Larry
Larry Jones wrote:
Diego Sevilla Ruiz writes [quoting me]:
If not, how did you
checkout dir1, dir2, and dir3?
Yes.
"Yes" is not an appropriate answer to "how".
Oh, again sorry... Human beings sometimes make mistakes... I
Diego Sevilla Ruiz writes:
Oh, again sorry... Human beings sometimes make mistakes... I do a "cvs
checkout ." in the root directory of my local copy of the CVS. Does
this answer to your question?
So, let me make sure I have this straight -- your $CVSROOT directory
looks something like:
I'm hoping that someone can suggest what I can do next.
I have CVS 1.10 on a sun unix box. I am using it 'directly' (i.e.
not client/server). I imported a large and heavily edited project and
was surprised to see a lot of *~ files end up in the repository. This
seems to contradict the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Larry!
Larry Jones wrote:
Diego Sevilla Ruiz writes:
Oh, again sorry... Human beings sometimes make mistakes... I do a "cvs
checkout ." in the root directory of my local copy of the CVS. Does
this answer to your question?
So, let me
[EMAIL PROTECTED] writes:
I have CVS 1.10 on a sun unix box. I am using it 'directly' (i.e.
not client/server). I imported a large and heavily edited project and
was surprised to see a lot of *~ files end up in the repository. This
seems to contradict the documentation which implies an
This theory does not hold if more than one tag is on the latest revision of a
file. It also does not indicate the latest tag across all branches. It does
not appear that the date of a tag is stored in the ,v file, so it is probably
not possible to always determine the latest tag.
Rex.
Rex Jolliffe wrote:
This theory does not hold if more than one tag is on the latest
revision of a
file. It also does not indicate the latest tag across all
branches. It does
not appear that the date of a tag is stored in the ,v file, so
it is probably
not possible to always determine the
With the advent of (idiotic) paths with spaces in them, it's become important to
deal with them.
I was thinking of the following style rule for calling executables:
1. When calling executables, wrap the executable name in double quotes. This is
even more important if a macro is being used
You probably want to use "cvs import -I*~ ..." instead if .cvsignore.
Michael
[EMAIL PROTECTED] wrote:
I'm hoping that someone can suggest what I can do next.
I have CVS 1.10 on a sun unix box. I am using it 'directly' (i.e.
not client/server). I imported a large and heavily
Thanks for your quick response. It was a clue from another respondant that
put me on the right track. Turns out I had a bad .cvsrc file in my home
directory. All is well with the world again (but I came -this- close to
using your suggestion!)
Tony Waite.
[ On Thursday, July 27, 2000 at 16:52:59 (-0400), Noel L Yap wrote: ]
Subject: general makefile (and script) style rule
Aside from "preventing" (ie ignoring) the problem, has anyone else found a good
way to deal with the situation?
Proactively seeking them out and destroying them is hardly
Ok now that's I've got about 6 different modules imported in CVS, I have 5
contractors and only want them to access certain modules, some should have
the ability to check them out and edit files, others just check out and
look, but don't touch.
Is there a way to do this? We all use
27 matches
Mail list logo
