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

temporarily unsetting sendemail.smtpuser

From
Eric Blake <eblake@redhat.com>
Date
May 19, 2010, 22:54 UTC
Message-ID
<4BF46C0A.9070000@redhat.com>

I have a setup where I normally send patches through my ISP, which requires authentication, so I have sendemail.smtpuser=me and sendemail.smtpserverport=587 set in my ~/.gitconfig (among others). But for one project I work on, I am required to send patches through an alternate SMTP server that does not require authentication.

At first, I thought it would be a simple matter to use git config to create an alias, where the explicit command line requests would override the global ~/.gitconfig settings:

[alias]
	submit = send-email --smtp-user= --smtp-server=alternate \
		--smtp-server-port=25
But that fails with:

$ git submit -1 fatal: unrecognized argument: --smtp-user= format-patch -o /tmp/JgTFO8Rq3v -1 --smtp-user=: command returned error: 128

In other words, git-send-email didn't recognize the empty --smtp-user= command as an override request, and instead passed it on to git-format-patch which croaks.

So I ended up creating this hairy alias instead:
[alias]
	submit = "!sh -c 'git config --global --unset sendemail.smtpuser; git
send-email --smtp-server=alternate --smtp-server-port=25 \"$@\"; st=$?;
git config --global sendemail.smtpuser me; (exit $st)' sh"
I suppose I could have used a shell function for fewer forks:
[alias]
	submit = "!doit() { git config --global --unset sendemail.smtpuser; git
send-email --smtp-server=alternate --smtp-server-port=25 \"$@\"; st=$?;
git config --global sendemail.smtpuser me; return $st; }; doit"

But both of those are rather unappealing. Is there a better approach to accomplishing what I wanted?

-- 
Eric Blake   eblake@redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org
Next: Ævar Arnfjörð Bjarmason
Message 1 of 2 in “temporarily unsetting sendemail.smtpuser”
  1. Eric BlakeMay 19, 2010
  2. Ævar Arnfjörð BjarmasonMay 20, 2010

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.