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

Re: Commit currently broken?

From: Ben Collins <bcollins_at_debian.org>
Date: 2002-04-07 01:50:40 CEST

On Sat, Apr 06, 2002 at 05:07:33PM -0600, cmpilato@collab.net wrote:
> cmpilato@collab.net writes:
>
> > David Summers <david@summersoft.fay.ar.us> writes:
> >
> > > OK, setting EDITOR environment variable to vi "fixed" the problem for me
> > > and I was able to commit.
> > >
> > > export EDITOR=vi
> > >
> > > Everything else except that is awesome....lots of progress in the last few
> > > weeks (I especially liked the "svn log" changes).
> > >
> > > Thanks!
> > > - David Summers
> >
> > That was the key, thanks. I just changed the way our $EDITOR stuff
> > works and forgot to test the case where there was no $EDITOR variable
> > set. I'll fix this *right now*.
>
> Actually, I should explain that statement a bit. On the phone
> yesterday, gstein, kfogel, sussman and I decided to remove the
> 'default fallbacks' for the $EDITOR (vi on Unix, notepad on Windows)
> so if a user doesn't want to be shocked by that popping up in their
> face, they can simply unset the environment variable. Instead of
> getting a default editor, they will get an error message that says
> that Subversion couldn't determine their external editor, and that
> they should either set the environment variable or use -m or -F.

So now instead they will get surprised by the difference between svn and
every other version control system? I can't think of one system that
doesn't do this already.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://linux1394.sourceforge.net/
Subversion - http://subversion.tigris.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 7 01:53:06 2002

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.