git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-send-email: allow overriding smtp-encryption config to 'none'

From
Brian Norris <computersforpeace@gmail.com>
Date
Feb 18, 2012, 05:27 UTC
Message-ID
<CAN8TOE-vek=ooq4DRcNF0iCg+rJMt6SUhMi4+_dOWaRJ44KLLA@mail.gmail.com>
In-Reply-To
<20120216004903.GA21170@sigill.intra.peff.net>
On Wed, Feb 15, 2012 at 4:49 PM, Jeff King <peff@peff.net> wrote:
> Ah, I see. I misunderstood the original problem you were trying to solve
> (I thought your example was "see? Encryption is off, so the server won't
> do AUTH, demonstrating that the patch works.").
Yeah, I got a little bit off track on what my actual goal was...
Show 5 quoted lines
> Overriding the smtp user from the config is a separate issue, and I
> don't think that is currently possible. The usual way to spell an option
> like that in git is "--no-smtp-user", but it seems that we use perl's
> GetOptions, which does not understand that syntax. So you'd have to add
> a "--no-smtp-user" by hand.

I think the "--no-smtp-user" is what I really wanted. I've written a different patch that actually targets the user name properly, but I've also found a current solution that can work for scripting purposes: just redirect the $GIT_CONFIG environment variable to /dev/null temporarily. Perhaps I'll send my new patch sometime, but it's not pressing and I'm not sure what kind of use it would actually get.

Thanks for the pointers.
Brian
Previous: Jeff KingNext: Jeff King
Message 5 of 6 in “git-send-email: allow overriding smtp-encryption config to 'none'”
  1. git-send-email: allow overriding smtp-encryption config to 'none'Brian Norris, Feb 15, 2012
  2. Jeff KingFeb 15, 2012
  3. Brian NorrisFeb 15, 2012
  4. Jeff KingFeb 16, 2012
  5. Brian NorrisFeb 18, 2012
  6. Jeff KingFeb 18, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.