[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: raises hand for bite-sized issue #604

From: <peter.westlake_at_arm.com>
Date: 2002-01-23 13:02:35 CET

On 2002-01-23 11:39:47 "Sander Striker" wrote:
>> 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 ;)

But then it isn't atomic. Yes, the log message is associated with the
entire
commit (or one directory's worth of files), but I like to say what I've
done
to each file. Even if all the edits are part of the same logical change,
the
implementation details are different from file to file. If the log for the
previous file is automatically inserted into the editor session for this
file,
it's very easy to skip past ones that don't need changing. Anyway, what's
so
special about a single directory that makes it sensible to have the
messages
the same for all files within it? Per-commit is sensible, and so is
per-file,
but per-directory is neither one thing nor the other.

>> 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.

No. But might it be possible to make the text of the earlier messages
available in a form readable by an ordinary editor? Is there a hook
somewhere, into which I could put a function/program to collect them?

Peter.

---------------------------------------------------------------------
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

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.