From: Eygene Ryabinkin <rea-git@codelabs.ru>
To: Eric Wong <normalperson@yhbt.net>
Cc: Sam Vilain <sam@vilain.net>, git@vger.kernel.org
Subject: Re: [PATCH] git-svn: respect Subversion's [auth] section configuration values
Date: Mon, 15 Oct 2007 11:17:50 +0400 [thread overview]
Message-ID: <20071015071750.GF984@void.codelabs.ru> (raw)
In-Reply-To: <20071007214334.GA7442@untitled>
Eric, good day.
Sun, Oct 07, 2007 at 02:43:34PM -0700, Eric Wong wrote:
> > Great, thanks for the pointer! Eric, do you want me to produce
> > another patch or you'll correct mine?
>
> Go ahead and produce another patch. I haven't had much time to
> work on git lately.
OK, the patch will follow in the separate thread. I had embedded
"no warnings 'once'" both to my new code and to your code to get
rid of the $kill_stupid_warnings. I did it selectively to minimize
the impact of the "no warnings" pragma.
--
Eygene
prev parent reply other threads:[~2007-10-15 7:18 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
2007-10-07 21:43 ` Eric Wong
2007-10-15 7:17 ` Eygene Ryabinkin [this message]
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=20071015071750.GF984@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).