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

Re: svn failing commit messages.

From: Mark H. Wilkinson <mhw_at_kremvax.net>
Date: 2003-01-13 19:54:10 CET

On Mon, 2003-01-13 at 10:25, Kevin Pilch-Bisson wrote:
> Maybe we should move commit messages to ~/.subversion/ instead of current
> directory. Then we would be able to leave the file around, and still be able
> to have a read-only source dir.

Hmm. A thought crosses my mind: one use-case that CVS never really
catered for, but which does happen every so often, is reusing the last
log message as the log message for a new commit. You know the kind of
thing: cd somewhere, commit a couple of files, cd somewhere else, commit
a couple of more that are part of the same logical group.

The extension of this is to have a (small) number of recent log messages
available if you want to retrieve text from them. I think one of the
Windows CVS GUIs (WinCVS?) provides this kind of history.

Anyway: how about storing a small number of recent log messages into the
~/.subversion/ directory, along with some noddy user interface during
the edit commit message process? I'm imagining something similar to the
CVS 'log message unchanged, abort, edit, commit' prompt that can be
accessed by exiting the editor immediately, through which you could
select one of the recent messages by number.

The import problem that started this thread would disappear, and the
user wouldn't need to know which special directory the log message was
dumped into...


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 14 12:26:47 2003

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.