From: Eygene Ryabinkin <rea-git@codelabs.ru>
To: Eric Wong <normalperson@yhbt.net>, Sam Vilain <sam@vilain.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-svn: respect Subversion's [auth] section configuration values
Date: Sun, 7 Oct 2007 14:14:37 +0400 [thread overview]
Message-ID: <20071007101437.GB3943@void.codelabs.ru> (raw)
In-Reply-To: <4708355B.4090403@vilain.net> <20071007032241.GG14972@hand.yhbt.net>
Eric, Sam, good day.
Sat, Oct 06, 2007 at 08:22:41PM -0700, Eric Wong wrote:
> Eygene Ryabinkin <rea-git@codelabs.ru> wrote:
> > Parameters 'store-passwords' and 'store-auth-creds' from Subversion's
> > configuration (~/.subversion/config) were not respected. This was
> > fixed: the default values for these parameters are set to 'yes' to
> > follow Subversion behaviour.
>
> Thanks.
You're welcome ;))
Sun, Oct 07, 2007 at 02:24:43PM +1300, Sam Vilain wrote:
> Eygene Ryabinkin wrote:
> > Parameters 'store-passwords' and 'store-auth-creds' from Subversion's
> > configuration (~/.subversion/config) were not respected. This was
> > fixed: the default values for these parameters are set to 'yes' to
> > follow Subversion behaviour.
> >
>
> I saw this in the svn api before. It really is a strange API, requiring
> the user to get things like this right.
Yes, the need to parse the configuration and set some flags is
rather strange. Looks like nobody cared to stuff the code like
I had added to the configuration file parsing routines.
> You can use no warnings 'once';
Great, thanks for the pointer! Eric, do you want me to produce
another patch or you'll correct mine?
--
Eygene
next prev parent reply other threads:[~2007-10-07 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 18:57 [PATCH] git-svn: respect Subversion's [auth] section configuration values Eygene Ryabinkin
2007-10-07 1:24 ` Sam Vilain
2007-10-07 3:24 ` Eric Wong
2007-10-07 3:22 ` Eric Wong
2007-10-07 10:14 ` Eygene Ryabinkin [this message]
2007-10-07 21:43 ` Eric Wong
2007-10-15 7:17 ` Eygene Ryabinkin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071007101437.GB3943@void.codelabs.ru \
--to=rea-git@codelabs.ru \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=sam@vilain.net \
/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.
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 NNTP newsgroup(s).