Re: log messages and --file-list (was: Re: raises hand for bite-sized issue #604)

On Wed, Jan 23, 2002 at 12:46:03PM -0800, Greg Stein wrote:
> On Tue, Jan 22, 2002 at 10:27:00AM -0600, cmpilato@collab.net wrote:
> > Mark Benedetto King <bking@answerfriend.com> writes:
> > > > On the other hand... I don't see why Karl is so paranoid about parsing
> > > > the log message and letting people remove parts of the commit. It
> > > > doesn't feel like a rat's nest to me.
> > >
> > > Me neither, but I'm willing to settle for the "--file-list" command-line
> > > argument. I'm also willing to provide a patch.
> >
> > As for parsing the log message, c'mon. When you run a command, say
> > what you mean, and mean what you say.
>
> What the heck are you saying here?
>
> By "parse the log message", I think we should strip the line that start with
> "SVN:", just like CVS does. And like CVS, we put the file list into lines
> with that prefix.

I believe Mike was objecting the the perforce style 'parse the log
message form and use it to figure out what files are commited' kind of
parsing, not the 'remove lines starting with SVN:' kind.

> > +1 on the "--file-list" argument though.
>
> +1 here. (of course, since I suggested it :-); the Win32 limits make me
> think it is almost a requirement for that platform)

The more i think about the Win32 limit (damn that's small!), the more
I think this is needed.

-garrett

-- 
garrett rooney                     Unix was not designed to stop you from 
rooneg@electricjellyfish.net       doing stupid things, because that would  
http://electricjellyfish.net/      stop you from doing clever things.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org