Attached. Documentation inside the script.
donald
On Thu, Nov 21, 2002 at 08:29:18AM +0200, Reinstein, Shlomo wrote:
Hi,
I found the check_cvs.pl script in some of the messages in the mailing-list.
Is this script published formally somewhere, or is that a private script
that was provided
Thanks, Donald, but I didn't mean to get an updated private version. I
really meant to ask if this script is going to be published (e.g., in the
contrib/ directory) and regularly updated.
One thing I'd add to the script is read the checkoutlist file and avoid
reporting the files specified there as
Go ahead and make the changes( if you want to ). I'll put them
into the copy I have. Publishing it into cvs is fine if someone
with write permission to the repository wants to do such a thing.
donald
On Thu, Nov 21, 2002 at 03:10:49PM +0200, Reinstein, Shlomo wrote:
Thanks, Donald, but I
Donald Sharp writes:
Publishing it into cvs is fine if someone
with write permission to the repository wants to do such a thing.
We can't do that given the current copyright notice; we need permission
to distribute it (preferably under the GPL).
-Larry Jones
All girls should be shipped to
Hi all,
I have a problem with my CVS repository that I don't understand: I have
a branch called forv_ver1_020311-branch in a module named itp which
has been in use for quite a while (as you can tell from the name).
I have created a local sandbox of this branch with the following:
cvs co -r
I would suggest that the forv_ver1_02X branch tag
doesn't exist in the first two directories. Since it
looks like you know the date when the tag was applied
you can pull a workspace with the cvs co -D date command
for those two directories and then apply the branch tag.
Then you should be
Donald Sharp wrote:
I would suggest that the forv_ver1_02X branch tag
doesn't exist in the first two directories. Since it
looks like you know the date when the tag was applied
you can pull a workspace with the cvs co -D date command
for those two directories and then apply the branch tag.
=?ISO-8859-1?Q?Karl-K=F6nig_K=F6nigsson?= writes:
As you can see is the branch treated as a tag in two of these, whereas
it is a branch in the rest. This has the upshot that it is impossible to
add files to the first two directories in this branch, but quite
allright in the other three.
Hi,
I have this messages on my screen after doing cvs update -dA:
cvs update: checksum failure after patch to ./myfile.txt; will refetch
But the refetch does not happen. However, if I change dir to where that
file is (lower in the directory hierarchy), I get this message instead:
cvs server:
I have been asked to tag (and branch) a module. The
Problem is that there are no current tags for that
build they want to branch on.
Can I, using Rtag -D , specifiy a date/time of the
build and tag all the files that were current on that
date/time then create a branch?
HELP!
Matt Rich
Greetings,
I notice that checkout.c, below the comment /* strip the last_component
*/ still uses strdup() instead of xstrdup(). Is this an accedent? FWIW,
OS/400 documents strdup() as an XPG4 extension.
Speaking of compiler warnings ... Does anybody still build cvs with a
compiler which does
Hello,
We have two repositories which need to be merged in to a single
database.
But i would like to retain the logs, tags and other info contained by
both database.
Is this possible ?
Any help is welcome.
I have tried to explain the problem in brief here.
We
Srinivas P Shenoy wrote:
We have two repositories which need to be merged in to a single
database.
But i would like to retain the logs, tags and other info contained by
both database.
Is this possible ?
Any help is welcome.
I have tried to explain the problem in brief here.
is it possible to
13 matches
Mail list logo
