Re: diff in commit message (was: Multiple-line log message)

2000-10-24 Thread Gerhard Sittig
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 showi

Re: diff in commit message (was: Multiple-line log message)

2000-10-24 Thread Richard J. Duncan
> 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 commit

Re: diff in commit message (was: Multiple-line log message)

2000-10-24 Thread Mike Castle
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 probab

Re: diff in commit message (was: Multiple-line log message)

2000-10-26 Thread Derek R. Price
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 wo

Re: diff in commit message (was: Multiple-line log message)

2000-10-26 Thread Derek R. Price
"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 lo

Re: diff in commit message (was: Multiple-line log message)

2000-10-26 Thread Gerhard Sittig
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 backgroun

Re: diff in commit message (was: Multiple-line log message)

2000-10-27 Thread Larry Jones
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'',

Re: diff in commit message (was: Multiple-line log message)

2000-10-27 Thread Gerhard Sittig
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

Re: diff in commit message (was: Multiple-line log message)

2000-10-28 Thread Larry Jones
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

Re: diff in commit message (was: Multiple-line log message)

2000-10-29 Thread Gerhard Sittig
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 wi

Re: diff in commit message (was: Multiple-line log message)

2000-10-30 Thread Gerhard Sittig
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: http://