From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Glenn Morris <rgm@gnu.org>
Cc: Carsten Bormann <cabo@tzi.org>, 13513@debbugs.gnu.org
Subject: bug#13513: 24.3.50; Going "--non-interactive" is the wrong thing for SVN on OSX
Date: Tue, 22 Jan 2013 14:00:27 -0500 [thread overview]
Message-ID: <jwv7gn52gki.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <lpa9s1dugl.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 22 Jan 2013 11:59:54 -0500")
>> [...] I agree that hardcoding --non-interactive is wrong.
>> We should probably make it a defcustom
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9993#11
>>> Perhaps we should just add --non-interactive to vc-svn-global-switches
>> That's a user var, so better leave it alone.
Oh, indeed, we could also just use vc-svn-global-switches rather than
introducing a new var. But as noted, changing such user var's default
is likely not to work for all users.
If the default should be "don't use --non-interactive", then we can just
drop the hardcoded --non-interactive and tell people to adjust their
vc-svn-global-switches if they want to pass --non-interactive.
So, could someone explain to me when --non-interactive is needed?
The report seemed to be for w32, does that mean that it's only ever needed
for w32, or is it also sometimes needed under GNU/Linux?
Stefan
next prev parent reply other threads:[~2013-01-22 19:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 13:25 bug#13513: 24.3.50; Going "--non-interactive" is the wrong thing for SVN on OSX Carsten Bormann
2013-01-22 2:02 ` Glenn Morris
2013-01-22 7:06 ` Carsten Bormann
2013-01-22 14:57 ` Stefan Monnier
2013-01-22 16:59 ` Glenn Morris
2013-01-22 19:00 ` Stefan Monnier [this message]
2013-01-23 8:41 ` Glenn Morris
2013-01-23 8:46 ` Glenn Morris
2013-01-23 21:53 ` Carsten Bormann
2013-01-30 16:42 ` Stefan Monnier
2013-01-30 17:02 ` Glenn Morris
2013-01-30 20:58 ` Stefan Monnier
2013-01-30 21:07 ` Glenn Morris
2013-01-30 21:10 ` Glenn Morris
2013-02-11 1:08 ` Glenn Morris
2013-01-22 18:14 ` Glenn Morris
2013-01-22 22:09 ` Carsten Bormann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv7gn52gki.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=13513@debbugs.gnu.org \
--cc=cabo@tzi.org \
--cc=rgm@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).