On Sun, Oct 29, 2000 at 09:00 +0100, Gerhard Sittig wrote:
There's a file /usr/src/contrib/cvs/FREEBSD-upgrade (if only I
had the bookmark around with the web frontend to the FreeBSD
source repo -- I can provide it on Tuesday) with the most
important section for you at its end:
On Sat, Oct 28, 2000 at 22:30 -0400, Larry Jones wrote:
[ ... ] I have no idea what the FreeBSD folks have done to
CVS, but it appears that they have at least added a global
option. To my knowledge, they've made no attempt to get input
from the CVS developers or share their changes with
Gerhard Sittig writes:
On Fri, Oct 27, 2000 at 10:48 -0400, Larry Jones wrote:
There's no such option in standard CVS -- you should use -n (which
^^
What does that mean? I researched this on a FreeBSD 4.1 system with
[...]
The manpage has no hint
Gerhard Sittig writes:
You pushed me in the right direction! Although -n means "don't
actually do it", I found out about the (general) -R option for
"the repo is on a ro medium".
There's no such option in standard CVS -- you should use -n (which
means ``don't modify stuff on the disk'',
On Fri, Oct 27, 2000 at 10:48 -0400, Larry Jones wrote:
Gerhard Sittig writes:
You pushed me in the right direction! Although -n means "don't
actually do it", I found out about the (general) -R option for
"the repo is on a ro medium".
There's no such option in standard CVS -- you
Mike Castle wrote:
On Tue, Oct 24, 2000 at 08:54:37PM +0200, Gerhard Sittig wrote:
Does anyone know a method how to incorporate "cvs diff" into the
"cvs commit" message and thus aid the committer with showing what
has changed when he is asked to specify what he did and why?
I would have
"Derek R. Price" wrote:
Still, if you really want to try it, I have a patch built on top of my *info
stuff that adds a tmpltfilterinfo file which works like loginfo and the rest
but provides a filter script which accepts the text from rcsinfo on stdin and
spits out the new text for the log
On Tue, Oct 24, 2000 at 14:21 -0500, Richard J. Duncan wrote:
Does anyone know a method how to incorporate "cvs diff" into
the "cvs commit" message and thus aid the committer with
showing what has changed when he is asked to specify what he
did and why?
As a background: At the
On Mon, Oct 23, 2000 at 14:59 -0500, Giang, Richard P wrote:
Does anyone know how to enter a log message that expands
multiple lines using command line cvs commit -m?
Does anyone know a method how to incorporate "cvs diff" into the
"cvs commit" message and thus aid the committer with showing
On Tue, Oct 24, 2000 at 08:54:37PM +0200, Gerhard Sittig wrote:
Does anyone know a method how to incorporate "cvs diff" into the
"cvs commit" message and thus aid the committer with showing what
has changed when he is asked to specify what he did and why?
I would have to say, this is probably
Does anyone know how to enter a log message that expands multiple lines
using command line cvs commit -m?
Thanks
Richard Giang
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Does anyone know how to enter a log message that expands multiple lines
using command line cvs commit -m?
It all depends on what shell you're using. try doing
cvs -m 'this is\
a long message' mod1 mod2...
___
Info-cvs mailing list
[EMAIL
12 matches
Mail list logo
