> On 2002-01-22 19:14:49 Daniel Stenberg wrote:
> ....
> >The subject of the issue is "Need something like CVS's $EDITOR
> >functionality".
> >
> >If anyone has any particular ideas or embryos, pass em on, or stay clear!
> ;-)
>
> From my limited experience with CVS it seems that it only pops up an editor
> once for each directory being committed, and all files in that get the same
> log message. I would very much prefer to have an editor instance per file.
/me shudders at that thought
AFAIK the log message is associated with the entire commit (which is atomic,
unlike cvs). Splitting out log messages per file will be a pain. If you
want this, commit per file ;)
> I've used a source control system which ran as an interactive command line
> program, with rudimentary editing facilities for log messages built in (as
> well as being able to invoke an editor). The nice thing about it was that
> it had escape sequences, like tilde escapes in "mail". The most useful one
> was the ability to call up the messages for earlier files and use them as
> a basis for the current one. That might be hard to do with a separate
> editor process, unless it had access to a set of temporary files containing
> the texts.
I don't think anyone feels like writing a portable editor, just for log
messages.
> Peter.
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:58 2006