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

[PATCH] send-email: simplify Gmail example in the documentation

From
Michal Nazarewicz <mina86@mina86.com>
Date
Apr 7, 2018, 10:07 UTC
Message-ID
<20180407100723.2168-1-mina86@mina86.com>
In-Reply-To
<20180404211446.GC15402@sigill.intra.peff.net>

There is no need for use to manually call ‘git credential’ especially as the interface isn’t super user-friendly and a bit confusing. ‘git send-email’ will do that for them at the first execution and if the password matches, it will be saved in the store.

Simplify the documentaion so it dosn’t include the ‘git credential’ invocation (which was incorrect anyway as it should use ‘approve’ instead of ‘fill’) and instead just mentions that credentials helper must be set up.

Signed-off-by: Michał Nazarewicz <mina86@mina86.com>
---
 Documentation/git-send-email.txt | 16 ++++++----------
 1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index 71ef97ba9..af07840b4 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git-send-email.txt
@@ -473,16 +473,7 @@ edit ~/.gitconfig to specify your account settings:

 If you have multifactor authentication setup on your gmail account, you will
 need to generate an app-specific password for use with 'git send-email'. Visit
-https://security.google.com/settings/security/apppasswords to setup an
-app-specific password.  Once setup, you can store it with the credentials
-helper:
-
-	$ git credential fill
-	protocol=smtp
-	host=smtp.gmail.com
-	username=youname@gmail.com
-	password=app-password
-
+https://security.google.com/settings/security/apppasswords to create it.

 Once your commits are ready to be sent to the mailing list, run the
 following commands:
@@ -491,7 +482,11 @@ following commands:
 	$ edit outgoing/0000-*
 	$ git send-email outgoing/*

+The first time you run it, you will be prompted for your credentials.  Enter the
+app-specific or your regular password as appropriate.  If you have credential
+helper configured (see linkgit:git-credential[1]), the password will be saved in
+the credential store so you won't have to type it the next time.
+
 Note: the following perl modules are required
       Net::SMTP::SSL, MIME::Base64 and Authen::SASL
-- 
2.16.2
Previous: Jeff KingNext: Michał Nazarewicz
Message 5 of 7 in “send-email: report host and port separately when calling git credential”
  1. send-email: report host and port separately when calling git credentialMichal Nazarewicz, Mar 31, 2018
  2. Junio C HamanoApr 2, 2018
  3. send-email: fix docs regarding storing password with git credentialMichal Nazarewicz, Apr 2, 2018
  4. Jeff KingApr 4, 2018
  5. send-email: simplify Gmail example in the documentationMichal Nazarewicz, Apr 7, 2018
  6. Michał NazarewiczApr 7, 2018
  7. Jeff KingApr 4, 2018

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.