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

Re: [PATCH] Re: Adding unversioned items to the log message

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: Mon, 22 Sep 2008 11:04:53 -0700

2008/9/22 Clint Lawrence <clint.lawrence_at_gmail.com>:
> I've expanded my original patch a little and now externals and ignored
> items are handled correctly. The only major task that still needs to be
> completed is disabling the search for unversioned items when it's not
> required.

Sorry for ignoring this thread until now - it just dawned on me what
this thread is discussing.

Can I add in my $.02 that I would absolutely not like to see this
functionality added by default? I have *lots* of unversioned (and
unignored) files in a lot of my WCs. I do not want to see my log
message template get consistently cluttered with that information.
For example, *just* in my Subversion WC, I have 31 '?' files - most of
these are patches and other notes to myself. (For $WORK, I have 120
such files in my main working copy directory.)

In the issue, Ben's example of TortoiseSVN being a good example of the
worthiness of always including this is something I disagree with -
TortoiseSVN is a UI that lets you change or modify the committable
list while you are writing the log message. When we invoke
$SVN_EDITOR, we don't have that ability (though we have talked about
it before). Plus, TortoiseSVN has the functionality to hit a checkbox
and all of the unversioned items go away. Guess what setting I use
with TortoiseSVN? *grin*

Therefore, if we have to add this, can we please have a knob that
turns this feature on (or off, if we do decide that including it is
best)? -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-22 20:05:06 CEST

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