"Derek R. Price" schrieb:
[...]
As for suggestions, you could probably script something over CVS if you
didn't want to hack the client/server. Have the script check the new file in
as binary (-kb) and then use the dreaded 'cvs admin -o' to delete revision
1.1, if it exists. That should be
From: [EMAIL PROTECTED]
Hi,
As far as I know, people don't use CVS for databases.
A simple 300MB database might take up many gigs after
just a few revisions. You're better off using the programs
the database comes with for version control and backup
I was not thinking about a populated
If the requirement is to be able to commit large binary files regardless
of the method used to store them, then there may be a tweak to the CVS
configuration available. If the requirement really is to disable version
history, then you're out of luck for the moment.
With regard to the
there is no api. Cvs client server works via STDIN/STDOUT redirection.
This is why you need to have cvs run by inetd. Inetd provides the
hookup of the pipes between STDIN/STDOUT and the sockets
Figure out what you want to do and fork/exec the apropriate cvs command.
donald
On Wed, Mar
I'm trying to write a dll to use with cold fusion... I'm guessing that sending
normal commands wouldn't be very efficient
GaRy
Donald Sharp wrote:
Why not just use the normal cvs commands?
donald
On Tue, Mar 28, 2000 at 09:06:11PM -0500, Gary Pinkham wrote:
Anyone out there
Title: RE: Executable Copy of file in Repository
If you are using the email address of [EMAIL PROTECTED], please delete this from your list. It is not a valid email address and our system is resolving the name to someone who does not want this mail.
Appreciate your assistance in this matter
So if I want a
CVS to store this copy as it is in some other directory so that I can
source this file from that directory, how do I do it?
Jagan,
This is a very common requirement. In the Per Cederqvist manual, read the
section titled, "Keeping a Checked-Out Copy".
-- Kevin Andrew Lipscomb
J. Brent Spears writes:
What causes the following error:
Protocol error: misformed Notify request.
The CVS server receiving a misformed Notify request. ;-)
Usually, that's caused by having edits or watches in a directory that
contains an "invalid" character: "+", ",", "", ";", "=", tab,
Greg Woods wrote:
[smc] [...]
My view of it was that currently HEAD appears to mean the head
of the trunk, with the one exception being that "cvs diff" treats it
differently. So my reasoning was to "fix" that one excetption, is
all.
The question is how many
Greetings!
Our developers will tag their code for builds under test, and when problems
are fixed, they will move the current tag until the product is shipped and
the tag is frozen. Occasionally, someone makes the mistake of moving the
branch tag instead of one of the branch's static tags.
I have a strange problem when trying to graft new subtrees onto
an existing CVS-managed tree, from within my CVS working
directories.
I am using client-server CVS - the version that comes with Red Hat 6.1 (1.10.2)
and ssh between the client and server (CVS_RSH=ssh).
I have a tree already under
[ On Wednesday, March 29, 2000 at 10:59:32 (-0600), Cameron, Steve wrote: ]
Subject: RE: Proposed new aliases, like HEAD
Either interpretation of HEAD is pretty simple to code, _if I'm right_.
Just a matter of calling rcs_head() or rcs_branch_head() for the "HEAD"
specific
Greg Woods, CVS guru, wrote:
[...]
If somebody is interested, I can try to make a version of my patch
that
makes HEAD work as it does for "cvs diff" in all the other cases. I
don't
think it's very hard. (Hardest part will probably be fixing
sanity.sh...)
I'd
From: Lukas Gruetzmacher [EMAIL PROTECTED]
Subject: bug in rlog?
Date: Thu, 30 Mar 2000 00:32:35 +0900 (JST)
| I think I've found a bug in rlog - May be is a feature... (I hope a talk
| about a rcs tool is welcome on this list.)
This is specification of RCS file. See man page rcsfile(5).
The simple answer is to run the merge from the branch to the trunk again,
but in reverse.
First, say you decide to put a new feature into development in its own
branch.
The branch is called 'FEATURE-1'
ocvs tag -b FEATURE-1
To easily back it out later, you also need a regular tag on
[ On Wednesday, March 29, 2000 at 15:00:19 (-0800), [EMAIL PROTECTED] wrote: ]
Subject: RE: Proposed new aliases, like HEAD
I thought I read recently (either in Cederqvist, the CVS FAQ, or this list) that
using "-r 1" was unsupported and not guarenteed to work in all versions of CVS,
[ On Wednesday, March 29, 2000 at 17:07:54 (-0600), David Thornley wrote: ]
Subject: Re: Disable "cvs tag -F" of branch tags
Yup. About fifteen minutes ago, I typed the wrong tag and changed
a branch tag into a normal tag. This would not have happened if
the restriction above had been in
On Wednesday, March 29, Donald Sharp wrote:
there is no api. Cvs client server works via STDIN/STDOUT redirection.
This is why you need to have cvs run by inetd. Inetd provides the
hookup of the pipes between STDIN/STDOUT and the sockets
Ok, there are at least 1 wrong statement in here.
On Wednesday, March 29, "J. Brent Spears" wrote:
What causes the following error:
Protocol error: misformed Notify request.
I use cvs on windows98 and wincvs. happens with both.
Hmm, if you are using the "rsh" method (which I'm not sure exists on
the wintel side), then I'd hazard a guess
I guess I confused the matter when I said api... What I wanted to see was a
simple example of using the protocol through a socket...
Thanks
GaRy
Donald Sharp wrote:
I said 'there is no api' because the guy sounded like he wanted
a api specification/header files and a library to link
20 matches
Mail list logo
