From: Carsten Bormann <cabo@tzi.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 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 08:06:23 +0100 [thread overview]
Message-ID: <83BD3F4A-FD6A-4592-A1E1-1629DBEE3B0B@tzi.org> (raw)
In-Reply-To: <5h622qht57.fsf@fencepost.gnu.org>
On Jan 22, 2013, at 03:02, Glenn Morris <rgm@gnu.org> wrote:
> Carsten Bormann wrote:
>
>> Checking in with vc-next-action in OSX with SVN backend often simply
>> fails with an authentication error. This is mostly unnecessary, as OSX
>> SVN knows how to interactively obtain authentication.
>>
>> Commenting out the forced "--non-interactive" in vc-svn-comment fixes this:
>
> That's not really an option; eg
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9993
Sure.
I understand why the change was made, it is just the wrong thing in those environments that don't have the bug being compensated for.
This is a bug report, so I didn't want to suggest one of the obvious solutions such as either of:
-- OS sensitivity;
-- a customize option;
-- a customize option that defaults to the right thing in an OS-sensitive way.
Your decision.
I just don't want to have to monkey-patch the code in eternity...
Grüße, Carsten
next prev parent reply other threads:[~2013-01-22 7:06 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 [this message]
2013-01-22 14:57 ` Stefan Monnier
2013-01-22 16:59 ` Glenn Morris
2013-01-22 19:00 ` Stefan Monnier
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=83BD3F4A-FD6A-4592-A1E1-1629DBEE3B0B@tzi.org \
--to=cabo@tzi.org \
--cc=13513@debbugs.gnu.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).