Larry,
Sorry for the repost, but I didn't get a specific response
from you on this, so I thought I would repost a shorter and
hopefully clearer message. Please see below. Thanks
Chuck
deleted
For each release, we tag our repository, so say I have tags R1 and
R2.
Passing -rR1:R2 to
For a new release of our software, we would like to get a listing of
log messages of all revisions since the last release. Our release
builds typically take place on a branch.
Since this seems like such a common place thing to do, I figured that
CVS would have a mechanism to support it. I'm
-Original Message-
From: larry.jones [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 06, 2001 4:03 PM
To: Chuck.Irvine
Cc: info-cvs; larry.jones
Subject: Re: logs of revisions since release
[EMAIL PROTECTED] writes:
For each release, we tag our repository, so say I
deleted
*** Invoke the following to see all revision logs
*** on branch br between r1.1 and r1.1. Keep in
*** mind that since foobar hasn't changed on the
*** branch, two subsequent branch tags would
*** point to the revision branched on.
cvs log -r1.1::1.1 -r1.1 foobar
RCS file:
I need to write a script that produces a list of everyone that has
commited to a branch (or the trunk) for a specific file. Before I and
write it, I thought I would check if anyone on the list already has
something like this laying around. Any help is much appreciated. Thanks
Chuck
Shubho,
Sometime ago, I posted patches by John Cavanaugh that can be used for
branch locking. The patches are for version 1.11 of CVS but work for the
most current version as well. One chunk of the patch will fail because a
file has been removed (actually, merged into another), but I have
Sonya,
I don't believe that it is possible to do what you are trying to do,
but in any case, you shouldn't need to. What are you trying to
accomplish? There is most likely a supported means to do the same
thing.
Chuck+
-Original Message-
From: sonya31 [mailto:[EMAIL PROTECTED]]
Why not use cvs remove?
-Original Message-
From: jeeva [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 22, 2001 11:55 AM
To: info-cvs
Cc: jeeva
Subject: hidding file from checkout
Hi,
I have tones of obsoleted file in my repository, I don't want the
developers to get them
See http://cvshome.org/docs/manual/cvs_5.html#SEC61.
Chuck
-Original Message-
From: bmccann [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 10, 2001 10:45 AM
To: info-cvs
Cc: bmccann
Subject: Merging mulitiple times
Hi,
I'm using WinCvs ver 1.2 here's my question which
Here is the place to start: http://cvshome.org/docs/
Chuck
-Original Message-
From: Jackie.Bilicic [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 09, 2001 9:39 AM
To: info-cvs
Subject: New CVS User
Hello all. I am a VERY new user to CVS. I was told by my employer to
begin
I'm considering updating our server to cvs-1.11.1p1, but it will be
very inconvenient to update all of our cvs clients that are at v1.11.
Can anyone tell me whether running 1.11 clients against a 1.11.1p1
server will/might cause me problems? Thanks
Chuck
Scott,
These basic concepts are covered very well in the cvs documentation.
Please see http://cvshome.org/docs/. Thanks
Chuck
-Original Message-
From: scott.johnson1 [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 03, 2001 4:04 PM
To: info-cvs
Subject: Understanding Branches and
Thanks for the input. I'll try to build and install 1.11.1.
-Original Message-
From: bjacob [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 01, 2001 8:41 PM
To: Chuck.Irvine
Cc: bjacob; info-cvs; bug-cvs
Subject: Unexpected merge conflict - bug maybe?
[EMAIL PROTECTED] writes:
I would appreciate help understanding how the merge conflict
that I am about to describe can logically happen. (I am
using cvs 1.11).
The conflict involves two branches, BRANCH, and a sub-branch
of BRANCH, SUB_BRANCH. So far, here's the history of the
two branches.
- Created SUB_BRANCH
Yes, we check them in. It's much easier then sending the out the actual
files. Why does this surprise you?
-Original Message-
From: zsmith [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 25, 2001 1:04 PM
To: Chuck.Irvine
Cc: zsmith; info-cvs
Subject: Re: Merge Management
You are right, of course, about destabilization. For this reason, we
almost always make conflict resolution our top priority. When this
isn't possible an alternative would be to branch off of your stable
stream and merge to this. After you've resolved merge conflicts, you
should be able to
See http://www.cvshome.com/communication.html
-Original Message-
From: rnanca [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 24, 2001 9:28 AM
To: info-cvs
Cc: rnanca
Subject: (no subject)
Please add to mailing list.
___
http://www.cvshome.com/dev/codewindow.html
-Original Message-
From: richard [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 23, 2001 11:02 AM
To: info-cvs
Cc: richard
Subject: Setting up a cvs server on Windows NT 4.0
can you point me in the right directtion?
thanks
I've heard this question many times and wonder if it is motivated by an
incorrect notion of the function of CVS checkout. Checkout gets a
"snapshot" of a module and places it in a local directory. It doesn't
reserve editing ability with regard to checked out files to just one
person. In other
Go to http://www.cvshome.org/communication.html#maillists and subcribe
to [EMAIL PROTECTED]
-Original Message-
From: mmrao12 [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 18, 2001 3:14 PM
To: info-cvs
Cc: mmrao12
Subject: (no subject)
Can you please include me in this
i solved the problem by replacing the cvs2ntslib.dll in the
wincvs-dir with
the one from cvsnt.
Sascha,
What do you mean by "the one from cvsnt"? Thanks
Chuck
Sascha,
I'm having a similar problem, but I am under the impression that it is
related to an incompatibility between cygwin's cvs.exe and WinCVS, the
problem being related to the timestamps the these two application
formulate. However, early on the the diagnosis of my problem, David
(sorry,
There are obviously some areas where CVS can be improved - no doubt.
But if you compare it to some other commercial SCM system that I'm
familiar with, e.g. ENVY that comes with IBM's Visual Age for Java or
PVCS, it is much, much superior. If ClearCase were free I'm pretty sure
that I would
-Original Message-
From: aspitzer [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 8:28 AM
To: info-cvs
Cc: aspitzer
Subject: more useful commitinfo info? i.e. branch-tag
Why is there not more useful information passed to cvs at commit time?
I think that the branch
Noel,
My group was recently enquiring into the possibility of implementing
some sort of CVS security. Would you mind giving some brief examples of
the kinds of things you can do with:
SSH
ACLs
I'm just looking for a little more detail than you provide below. This
will help me get my
We've just noticed that DOS line endings are finding their way into our
CVS repository (or maybe I don't fully understand how things are
supposed to work). Here is our configuration:
Client:
NT 4.0
cygwin/cvs 1.11
winCvs 1.2
The problem seems independent of whether we use cvs that comes with
Another method is cvs diff, something like:
cvs -q diff --brief
This gives you a little less extraneous data than does update.
Chuck
-Original Message-
From: r.burton [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 04, 2001 11:00 AM
To: graeme.vetterlein
Cc: info-cvs
Subject:
At any given time, we have multiple releases of our software under
development. Each release has it's own branch, with the latest release
being developed on the trunk. We propogate changes downstream by doing
merges from each release branch to the immediate downstream release
branch.
Here
Hello Earnie. The output of cygcheck is attached. Thanks. Chuck
cygcheck -s -r -v
Cygnus Win95/NT Configuration Diagnostics
Current System Time: Fri Mar 9 15:04:13 2001
WinNT Ver 4.0 build 1381 Service Pack 4
Path: /chuck/cvshome/setstools/bin
/cygdrive/c/programs/emacs-20.7/bin
WinCVS version 1.2 is incorrectly reporting that cvs controlled files
are locally modified. Interesting it only does this for some files and
not others. To check out files, I'm using the version of cvs.exe that
comes with cygwin (version 1.11). Any help is greatly appreciated.
Thanks
Chuck
I use the emacs "Tools-Version Control-Check In/Out" command to
commit file changes to CVS. When I invoke this command, I get a blank
buffer to enter log comments. Is there a way I can have the template
file specified in the rcsinfo file pre-inserted into this buffer. I'm
figuring there has
Mark,
Attached are patches to CVS 1.11 that cause additional information to
be passed to your commitinfo script, namely the branch being checked
into. If you are interested, patch, do a build, and search the newly
generated cvs*.info files for "AlternateInfo" for details on how to use
this
My main problem with "Import" is that it does not insert
all the metadata into my existing directory structure.
So once I import the stuff, I then have to move it out
of the way (rename the dir) and check everything out
again. "Add" takes care of this for me.
It seems that what is
See below for answers. Not much to it. Send beers to John :-)
2) Modify 'CVSROOT/commitinfo'. I know I need to add a line
that calls
the perl script, but I'm sketchy on the syntax of this.
Add something like:
^project-name fullDirectorySpec/nameOfBranchLockingScript
3) Modify
Vic,
The instructions are in the accompanying cvs.info* files that should
have been generated as a result of the make. Info files are
documentation files that are read via emacs. You can do a search of
"AlternateInfo" to find documentation relevant to this feature.
The perl script gets
I believe this is a known problem, at least it's a problem that we are,
unfortunately,
very familiar with at my site. It has nothing to do with WinCVS I
believe. My slightly vague understanding is that it has something to do
with CVS imperfectly dealing with the fact that files are case
See "-d" option for update -- Chuck
-Original Message-
From:peter.schuller [mailto:[EMAIL PROTECTED]]
Sent:Tuesday, January 30, 2001 2:34 PM
To: peter.schuller; info-cvs
Subject: 'cvs update' skipping directories
Hello,
For the past few months I've been seeing some
cvs log fileName
-Original Message-
From: kellydai99 [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 24, 2001 6:31 PM
To: info-cvs
Cc: kellydai99
Subject: looking history of checkin/checkout for a file
Is there a way of looking at the history of
checkin/checkout for a
David,
Even though CVS lets more than one developer edit a file at the same
time, it will not let develoers overwrite each others changes. And
that's what is important. Please read the CVS docs to understand the
philosophy and mechanics of this. If you are like so many, you will end
up
Ouch! I apologize for my transgression. I work in an environment where
we are spoiled by having immense communication bandwidth. I'll be more
considerate next time.
Chuck
Sprint
-Original Message-
From: dave [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 4:33 PM
To:
Hi John,
I had some success with the branch locking patches, but there were a
few glitches also. They were:
1. I couldn't get the patch to accept the combined patch file I
downloaded. My use of patch is limited to invoking "patch
patch-file", and that wouldn't work. I got past this problem
? These don't seem to listed on
http://www.cvshome.com/dev/patches.html. Why?
2. Since this is an often asked for feature, why couldn't John's patches
be folded in to the official release?
Many thanks in advance.
Chuck Irvine
Sprint
Say you've just checked in revision 1.2 of foo.txt. The way that
I would revert is:
$ cvs update -j 1.2 -j 1.1 foo.txt
$ cvs ci foo.txt
This gives you revision 1.3 which is the same as 1.1. I personally don't
like the idea of a rollback command that completely purges a particular
revision of a
Our project is organized into multiple overlapping streams of
development. At anytime there are at least two streams and as many as 4.
(We are doing this, you may have guessed, because we are in a hurry.
Please nevermind whether this is, in itself, is a good thing.)
Would anyone care to comment
One problem we experienced is that VAJ, upon extract to a CVS workspace,
would re-format the entire source file. This plays havac with CVS's
concept of simultaneous editing of the same file by different
developers, i.e. the probability of merge conflicts goes up
dramatically. This could force you
Derek is correct. Another downside, though, is that VAJ's formatting of
the code isn't very good. As I recall, it removes all blank lines and
the indentation is poor. So, people are always tempted to reformat. We
migrated away from VAJ before the new version came out - the one
supporting JDK1.2.
lem is due to an unexpected NT related side
effect.
Chuck Irvine
Sprint
-Original Message-
From: donald.coleman [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 21, 2000 1:55 PM
To: jde
Subject:Java buffers are randomly read-only
I don't know if this is a JD
Perhaps the problem is that the security functionality provided by the
OS isn't easily mapped to CVS administration functions, especially for
those who are more OS "users" versus those who have experience with OS
"administration".
For example, here are a few of the admin things we would like to
Is the Cederqvist manual available in downloadable form from somewhere?
Thank you.
Chuck Irvine
Sprint
When might the patch referred to below make it into a future CVS
release? Thanks
Chuck Irvine
Sprint
-Original Message-
From: chris.cameron [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 31, 2000 1:58 PM
To: ljnelson; smazur
Cc: info-cvs
Subject: RE: access rights to branches
50 matches
Mail list logo
