{"thread":{"id":"63454","subject":"[PATCH] docs: add instructions to use Yahoo with send-mail","startedAt":"2025-05-13T18:29:15Z","lastAt":"2025-05-30T21:55:22Z","messageCount":52,"participants":["Aditya Garg","Junio C Hamano","Eric Sunshine","Ben Knoble"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"517963","messageId":"PN3PR01MB95971131BD3CD89771F19E5DB896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":null,"subject":"[PATCH] docs: add instructions to use Yahoo with send-mail","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-13T18:28:44Z","receivedAt":"2025-05-13T18:29:15Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"Just like Gmail and Outlook, Yahoo is another popular email service\nprovider. This commit adds instructions for Yahoo users to be able\nto use it with `git send-email`. It also adds instructions for\nOAauth2.0 authentication for the same, and adds a link for a\ncredential helper.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/git-send-email.adoc | 32 +++++++++++++++++++++++++++++++\n Documentation/gitcredentials.adoc | 2 ++\n 2 files changed, 34 insertions(+)\n\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 26fda63c2f..61a2d03546 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -561,6 +561,35 @@ SMTP server with `git send-email`:\n \tsmtpAuth = XOAUTH2\n ----\n \n+Use Yahoo as the SMTP Server\n+~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n+Just like Gmail, you can use an app-specific password for Yahoo as well. Visit\n+https://help.yahoo.com/kb/SLN15241.html to get instructions for generating\n+them. After generating, edit `~/.gitconfig` to specify your account settings\n+for Yahoo and use its SMTP server with `git send-email`:\n+\n+----\n+[sendemail]\n+\tsmtpEncryption = tls\n+\tsmtpServer = smtp.mail.yahoo.com\n+\tsmtpUser = yourname@yahoo.com\n+\tsmtpServerPort = 587\n+----\n+\n+If you wish to use OAuth2.0 rather than an app-specific password, you can use\n+either `OAUTHBEARER` or `XOAUTH2` as the authentication method. As an example,\n+if you want to use `OAUTHBEARER`, edit your `~/.gitconfig` file and add\n+`smtpAuth = OAUTHBEARER` to your account settings:\n+\n+----\n+[sendemail]\n+\tsmtpEncryption = tls\n+\tsmtpServer = smtp.mail.yahoo.com\n+\tsmtpUser = yourname@yahoo.com\n+\tsmtpServerPort = 587\n+\tsmtpAuth = OAUTHBEARER\n+----\n+\n SENDING PATCHES\n ---------------\n Once your commits are ready to be sent to the mailing list, run the\n@@ -588,6 +617,9 @@ are also available:\n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook]\n \t (cross platform, dedicated helper for authenticating Microsoft Outlook accounts)\n \n+\t- https://github.com/AdityaGarg8/git-credential-email[git-credential-yahoo]\n+\t (cross platform, dedicated helper for authenticating Yahoo accounts)\n+\n You can also see linkgit:gitcredentials[7] for more OAuth based authentication\n helpers.\n \ndiff --git a/Documentation/gitcredentials.adoc b/Documentation/gitcredentials.adoc\nindex b49923db02..0c4fd0e8e7 100644\n--- a/Documentation/gitcredentials.adoc\n+++ b/Documentation/gitcredentials.adoc\n@@ -137,6 +137,8 @@ Popular helpers with OAuth support include:\n \n - https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook] (cross platform, dedicated helper to authenticate Microsoft Outlook accounts for linkgit:git-send-email[1])\n \n+ - https://github.com/AdityaGarg8/git-credential-email[git-credential-yahoo] (cross platform, dedicated helper to authenticate Yahoo accounts for linkgit:git-send-email[1])\n+\n CREDENTIAL CONTEXTS\n -------------------\n \n-- \n2.43.0\n\n"},{"id":"517965","messageId":"PN3PR01MB9597AEC10C20F4B06C4BE254B896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"PN3PR01MB95971131BD3CD89771F19E5DB896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"Re: [PATCH] docs: add instructions to use Yahoo with send-mail","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-13T18:33:59Z","receivedAt":"2025-05-13T18:34:06Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\nOn 13/05/25 11:58 pm, Aditya Garg wrote:\n> Just like Gmail and Outlook, Yahoo is another popular email service\n> provider. This commit adds instructions for Yahoo users to be able\n> to use it with `git send-email`. It also adds instructions for\n> OAauth2.0 authentication for the same, and adds a link for a\n> credential helper.\n> \n> Signed-off-by: Aditya Garg \n> ---\n> Documentation/git-send-email.adoc | 32 +++++++++++++++++++++++++++++++\n> Documentation/gitcredentials.adoc | 2 ++\n> 2 files changed, 34 insertions(+)\n> \n> diff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\n> index 26fda63c2f..61a2d03546 100644\n> --- a/Documentation/git-send-email.adoc\n> +++ b/Documentation/git-send-email.adoc\n> @@ -561,6 +561,35 @@ SMTP server with `git send-email`:\n> \tsmtpAuth = XOAUTH2\n> ----\n> \n> +Use Yahoo as the SMTP Server\n> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n> +Just like Gmail, you can use an app-specific password for Yahoo as well. Visit\n> +https://help.yahoo.com/kb/SLN15241.html to get instructions for generating\n> +them. After generating, edit `~/.gitconfig` to specify your account settings\n> +for Yahoo and use its SMTP server with `git send-email`:\n> +\n> +----\n> +[sendemail]\n> +\tsmtpEncryption = tls\n> +\tsmtpServer = smtp.mail.yahoo.com\n> +\tsmtpUser = yourname@yahoo.com\n> +\tsmtpServerPort = 587\n> +----\n> +\n> +If you wish to use OAuth2.0 rather than an app-specific password, you can use\n> +either `OAUTHBEARER` or `XOAUTH2` as the authentication method. As an example,\n> +if you want to use `OAUTHBEARER`, edit your `~/.gitconfig` file and add\n> +`smtpAuth = OAUTHBEARER` to your account settings:\n> +\n> +----\n> +[sendemail]\n> +\tsmtpEncryption = tls\n> +\tsmtpServer = smtp.mail.yahoo.com\n> +\tsmtpUser = yourname@yahoo.com\n> +\tsmtpServerPort = 587\n> +\tsmtpAuth = OAUTHBEARER\n> +----\n> +\n> SENDING PATCHES\n> ---------------\n> Once your commits are ready to be sent to the mailing list, run the\n> @@ -588,6 +617,9 @@ are also available:\n> \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook]\n> \t (cross platform, dedicated helper for authenticating Microsoft Outlook accounts)\n> \n> +\t- https://github.com/AdityaGarg8/git-credential-email[git-credential-yahoo]\n> +\t (cross platform, dedicated helper for authenticating Yahoo accounts)\n> +\n\nBTW, I could not get the source code for https://git-scm.com/doc/credential-helpers. It\nseems to be a page for all credential helpers.\n"},{"id":"517967","messageId":"xmqqzffgfj2m.fsf@gitster.g","threadId":"63454","inReplyTo":"PN3PR01MB9597AEC10C20F4B06C4BE254B896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"Re: [PATCH] docs: add instructions to use Yahoo with send-mail","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-05-13T18:42:57Z","receivedAt":"2025-05-13T18:43:00Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Aditya Garg writes:\n\n> BTW, I could not get the source code for https://git-scm.com/doc/credential-helpers. It\n> seems to be a page for all credential helpers.\n\nProbably\n\nhttps://github.com/git/git-scm.com/blob/gh-pages/content/doc/credential-helpers.html\n\nSee https://github.com/git/git-scm.com?tab=readme-ov-file#git-homepage--\nfor the general notes to get changes to that repository.\n"},{"id":"517969","messageId":"PN3PR01MB9597028D4430E9C2C2BB1E5FB896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"xmqqzffgfj2m.fsf@gitster.g","subject":"Re: [PATCH] docs: add instructions to use Yahoo with send-mail","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-13T18:51:57Z","receivedAt":"2025-05-13T18:52:07Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\nOn 14/05/25 12:12 am, Junio C Hamano wrote:\n> Aditya Garg writes:\n> \n>> BTW, I could not get the source code for https://git-scm.com/doc/credential-helpers. It\n>> seems to be a page for all credential helpers.\n> \n> Probably\n> \n> https://github.com/git/git-scm.com/blob/gh-pages/content/doc/credential-helpers.html\n> \n> See https://github.com/git/git-scm.com?tab=readme-ov-file#git-homepage--\n> for the general notes to get changes to that repository.\n\nThanks!\n\n"},{"id":"517980","messageId":"PN3PR01MB95977BF45DCF3E7F784FD909B896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"PN3PR01MB9597028D4430E9C2C2BB1E5FB896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"Re: [PATCH] docs: add instructions to use Yahoo with send-mail","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-13T19:36:13Z","receivedAt":"2025-05-13T19:36:21Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\nOn 14/05/25 12:21 am, Aditya Garg wrote:\n> \n> \n> On 14/05/25 12:12 am, Junio C Hamano wrote:\n>> Aditya Garg writes:\n>>\n>>> BTW, I could not get the source code for https://git-scm.com/doc/credential-helpers. It\n>>> seems to be a page for all credential helpers.\n>>\n>> Probably\n>>\n>> https://github.com/git/git-scm.com/blob/gh-pages/content/doc/credential-helpers.html\n>>\n\nOk so I'll just get the Yahoo docs merged before opening a PR in this repo.\n\n>> See https://github.com/git/git-scm.com?tab=readme-ov-file#git-homepage--\n>> for the general notes to get changes to that repository.\n> \n> Thanks!\n> \n"},{"id":"518030","messageId":"xmqqo6vvcprj.fsf@gitster.g","threadId":"63454","inReplyTo":"PN3PR01MB95971131BD3CD89771F19E5DB896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"Re: [PATCH] docs: add instructions to use Yahoo with send-mail","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-05-14T12:58:56Z","receivedAt":"2025-05-14T12:58:59Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Aditya Garg writes:\n\n> Just like Gmail and Outlook, Yahoo is another popular email service\n> provider. This commit adds instructions for Yahoo users to be able\n> to use it with `git send-email`. It also adds instructions for\n> OAauth2.0 authentication for the same, and adds a link for a\n> credential helper.\n\nHeh, I didn't know they are still around ;-)\n\n $ git checkout master\n $ for p in yahoo.com outlook.com gmail.com\n do\n echo \"@$p\"\n git log --oneline --since=5.years --no-merges --author=@$p |\n wc -l\n done\n @yahoo.com\n 12\n @outlook.com\n 16\n @gmail.com\n 4765\n\n> diff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\n> index 26fda63c2f..61a2d03546 100644\n> --- a/Documentation/git-send-email.adoc\n> +++ b/Documentation/git-send-email.adoc\n> @@ -561,6 +561,35 @@ SMTP server with `git send-email`:\n> \tsmtpAuth = XOAUTH2\n> ----\n> \n> +Use Yahoo as the SMTP Server\n> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n> +Just like Gmail, you can use an app-specific password for Yahoo as well. Visit\n> +https://help.yahoo.com/kb/SLN15241.html to get instructions for generating\n> +them. After generating, edit `~/.gitconfig` to specify your account settings\n> +for Yahoo and use its SMTP server with `git send-email`:\n\nI am starting to doubt the wisdom of giving one section per\nprovider, especially since the delta between the section is so small\n(essentially, the server address, the smtpAuth supported, and their\nofficial documentation URL). Would it make more sense to just have\na template example with placeholders, and a table of placeholder\nvalues that has one row per provider?\n\n> +\n> +----\n> +[sendemail]\n> +\tsmtpEncryption = tls\n> +\tsmtpServer = smtp.mail.yahoo.com\n> +\tsmtpUser = yourname@yahoo.com\n> +\tsmtpServerPort = 587\n> +----\n> +\n> +If you wish to use OAuth2.0 rather than an app-specific password, you can use\n> +either `OAUTHBEARER` or `XOAUTH2` as the authentication method. As an example,\n> +if you want to use `OAUTHBEARER`, edit your `~/.gitconfig` file and add\n> +`smtpAuth = OAUTHBEARER` to your account settings:\n"},{"id":"518033","messageId":"PN3PR01MB959774B05496F9BC3167162AB891A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"xmqqo6vvcprj.fsf@gitster.g","subject":"Re: [PATCH] docs: add instructions to use Yahoo with send-mail","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-14T13:05:58Z","receivedAt":"2025-05-14T13:06:06Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\nOn 14/05/25 6:28 pm, Junio C Hamano wrote:\n> Aditya Garg writes:\n> \n>> Just like Gmail and Outlook, Yahoo is another popular email service\n>> provider. This commit adds instructions for Yahoo users to be able\n>> to use it with `git send-email`. It also adds instructions for\n>> OAauth2.0 authentication for the same, and adds a link for a\n>> credential helper.\n> \n> Heh, I didn't know they are still around ;-)\n> \n> $ git checkout master\n> $ for p in yahoo.com outlook.com gmail.com\n\nYou may want to check for hotmail.com and live.com as well :)\n\n> do\n> echo \"@$p\"\n> git log --oneline --since=5.years --no-merges --author=@$p |\n> wc -l\n> done\n> @yahoo.com\n> 12\n> @outlook.com\n> 16\n> @gmail.com\n> 4765\n> \n>> diff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\n>> index 26fda63c2f..61a2d03546 100644\n>> --- a/Documentation/git-send-email.adoc\n>> +++ b/Documentation/git-send-email.adoc\n>> @@ -561,6 +561,35 @@ SMTP server with `git send-email`:\n>> \tsmtpAuth = XOAUTH2\n>> ----\n>> \n>> +Use Yahoo as the SMTP Server\n>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n>> +Just like Gmail, you can use an app-specific password for Yahoo as well. Visit\n>> +https://help.yahoo.com/kb/SLN15241.html to get instructions for generating\n>> +them. After generating, edit `~/.gitconfig` to specify your account settings\n>> +for Yahoo and use its SMTP server with `git send-email`:\n> \n> I am starting to doubt the wisdom of giving one section per\n> provider, especially since the delta between the section is so small\n> (essentially, the server address, the smtpAuth supported, and their\n> official documentation URL). Would it make more sense to just have\n> a template example with placeholders, and a table of placeholder\n> values that has one row per provider?\n\nUmm, not sure how to get that done. Don't have much experience in these docs yk.\n\nAlso, I don't intend to support more email providers.\n\nYou also might want to hold off this for a while since I opened a PR here:\n\nhttps://github.com/git/git-scm.com/pull/2005#issuecomment-2880140423\n\nAnd as per this, we might have to remove the email helper links, from\ngitcredentials, or move them to a separate section.\n\n> \n>> +\n>> +----\n>> +[sendemail]\n>> +\tsmtpEncryption = tls\n>> +\tsmtpServer = smtp.mail.yahoo.com\n>> +\tsmtpUser = yourname@yahoo.com\n>> +\tsmtpServerPort = 587\n>> +----\n>> +\n>> +If you wish to use OAuth2.0 rather than an app-specific password, you can use\n>> +either `OAUTHBEARER` or `XOAUTH2` as the authentication method. As an example,\n>> +if you want to use `OAUTHBEARER`, edit your `~/.gitconfig` file and add\n>> +`smtpAuth = OAUTHBEARER` to your account settings:\n\n"},{"id":"518094","messageId":"PN3PR01MB9597D6BAA98013269897A963B890A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"PN3PR01MB95971131BD3CD89771F19E5DB896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"[PATCH v2 0/2] docs: update email credential helpers","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-15T10:29:22Z","receivedAt":"2025-05-15T10:34:10Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"Hi all,\n\nThis patch series included two patches:\n\n1. The first patch adds a link to the `git-credential-yahoo` helper for\n Yahoo accounts and links Google's `sendgmail` tool as an alternative\n method for sending emails through Gmail.\n\n2. The second patch removed the email credential helper links from the\n `gitcredentials` page. The links are still available in the\n `git-send-email` documentation, which is the right place for them.\n\nDetailed explanation of the changes has been done in individual patch.\n\nv2: Removed instructions for Yahoo SMTP server since I've realised that\n Yahoo *was* a popular email service. Also, the instructions were\n just making the docs more crowded. I've also added a link to\n Google's `sendgmail` tool in the first patch. The second patch has been\n added to address the issues that came up here:\n https://github.com/git/git-scm.com/pull/2005\n\nAditya Garg (2):\n docs: add credential helper for yahoo and link Google's sendgmail tool\n docs: remove credential helper links for emails from gitcredentials\n\n Documentation/git-send-email.adoc | 10 ++++++++--\n Documentation/gitcredentials.adoc | 4 ----\n 2 files changed, 8 insertions(+), 6 deletions(-)\n\n-- \n2.49.0\n\n"},{"id":"518095","messageId":"PN3PR01MB9597F04CF39B1B95CA5AACE0B890A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"PN3PR01MB9597D6BAA98013269897A963B890A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"[PATCH v2 1/2] docs: add credential helper for yahoo and link Google's sendgmail tool","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-15T10:29:23Z","receivedAt":"2025-05-15T10:34:14Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"This commit links `git-credential-yahoo` as a credential helper for\nYahoo accounts. Also, Google's `sendgmail` tool has been linked as an\nalternative method for sending emails through Gmail.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/git-send-email.adoc | 10 ++++++++--\n 1 file changed, 8 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 26fda63c2f..81f8cbc6f3 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -543,6 +543,10 @@ settings:\n \tsmtpAuth = OAUTHBEARER\n ----\n \n+Alternatively, you can use a tool developed by Google known as\n+https://github.com/google/gmail-oauth2-tools/tree/master/go/sendgmail[sendgmail]\n+to send emails using `git send-email`.\n+\n Use Microsoft Outlook as the SMTP Server\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.\n@@ -579,8 +583,7 @@ next time.\n \n If you are using OAuth2.0 authentication, you need to use an access token in\n place of a password when prompted. Various OAuth2.0 token generators are\n-available online. Community maintained credential helpers for Gmail and Outlook\n-are also available:\n+available online. Community maintained credential helpers are also available:\n \n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail]\n \t (cross platform, dedicated helper for authenticating Gmail accounts)\n@@ -588,6 +591,9 @@ are also available:\n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook]\n \t (cross platform, dedicated helper for authenticating Microsoft Outlook accounts)\n \n+\t- https://github.com/AdityaGarg8/git-credential-email[git-credential-yahoo]\n+\t (cross platform, dedicated helper for authenticating Yahoo accounts)\n+\n You can also see linkgit:gitcredentials[7] for more OAuth based authentication\n helpers.\n \n-- \n2.49.0\n\n"},{"id":"518096","messageId":"PN3PR01MB95974833251AAE9531F8ED62B890A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"PN3PR01MB9597D6BAA98013269897A963B890A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"[PATCH v2 2/2] docs: remove credential helper links for emails from gitcredentials","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-15T10:29:24Z","receivedAt":"2025-05-15T10:34:16Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"In a recent attempt to add links of email helpers to git-scm.com [1], I\ncame to a conclusion that the links in the gitcredentials page are meant\nfor people needing credential helpers for cloning, fetching and pushing\nrepositories to remote hosts, and not sending emails. gitcredentials\ndocs don't even talk about send emails, thus confirming this view.\n\nSo, lets remove these links from the gitcredentials page. The links are\nstill available in the git-send-email documentation, which is the right\nplace for them.\n\n[1]: https://github.com/git/git-scm.com/pull/2005\n\nSigned-off-by: Aditya Garg \n---\n Documentation/gitcredentials.adoc | 4 ----\n 1 file changed, 4 deletions(-)\n\ndiff --git a/Documentation/gitcredentials.adoc b/Documentation/gitcredentials.adoc\nindex b49923db02..3337bb475d 100644\n--- a/Documentation/gitcredentials.adoc\n+++ b/Documentation/gitcredentials.adoc\n@@ -133,10 +133,6 @@ Popular helpers with OAuth support include:\n \n - https://github.com/hickford/git-credential-oauth[git-credential-oauth] (cross platform, included in many Linux distributions)\n \n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail] (cross platform, dedicated helper to authenticate Gmail accounts for linkgit:git-send-email[1])\n-\n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook] (cross platform, dedicated helper to authenticate Microsoft Outlook accounts for linkgit:git-send-email[1])\n-\n CREDENTIAL CONTEXTS\n -------------------\n \n-- \n2.49.0\n\n"},{"id":"518346","messageId":"6D57A8EA-FDE8-42C9-9541-7B97C2DDBCA1@live.com","threadId":"63454","inReplyTo":"PN3PR01MB9597D6BAA98013269897A963B890A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"[PATCH v3 0/3] docs: update email credential helpers and improve formatting","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-18T07:34:13Z","receivedAt":"2025-05-18T07:34:17Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"Hi all,\n\nThis patch series included three patches:\n\n1. The first patch adds a link to the `git-credential-yahoo` helper for\n Yahoo accounts and links Google's `sendgmail` tool as an alternative\n method for sending emails through Gmail.\n\n2. The second patch improves the formatting of the `git-send-email`\n documentation, making it more readable and consistent.\n\n3. The third patch removed the email credential helper links from the\n `gitcredentials` page. The links are still available in the\n `git-send-email` documentation, which is the right place for them.\n\nDetailed explanation of the changes has been done in individual patch.\n\nv2: Removed instructions for Yahoo SMTP server since I've realised that\n Yahoo *was* a popular email service. Also, the instructions were\n just making the docs more crowded. I've also added a link to\n Google's `sendgmail` tool in the first patch. The second patch has been\n added to address the issues that came up here:\n https://github.com/git/git-scm.com/pull/2005\n\nv3: Added a patch to improve the formatting of the `git-send-email`\n documentation.\n\nAditya Garg (3):\n docs: add credential helper for yahoo and link Google's sendgmail tool\n docs: improve formatting in git-send-email documentation\n docs: remove credential helper links for emails from gitcredentials\n\n Documentation/config/sendemail.adoc | 8 +-\n Documentation/git-send-email.adoc | 187 +++++++++++++++-------------\n Documentation/gitcredentials.adoc | 4 -\n 3 files changed, 102 insertions(+), 97 deletions(-)\n\n-- \n2.49.0\n\n"},{"id":"518351","messageId":"94643E90-49A6-4615-A82B-110A7D5297B1@live.com","threadId":"63454","inReplyTo":"6D57A8EA-FDE8-42C9-9541-7B97C2DDBCA1@live.com","subject":"[PATCH v3 1/3] docs: add credential helper for yahoo and link Google's sendgmail tool","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-18T07:35:27Z","receivedAt":"2025-05-18T07:35:32Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"This commit links `git-credential-yahoo` as a credential helper for\nYahoo accounts. Also, Google's `sendgmail` tool has been linked as an\nalternative method for sending emails through Gmail.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/git-send-email.adoc | 10 ++++++++--\n 1 file changed, 8 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 26fda63c2f..81f8cbc6f3 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -543,6 +543,10 @@ settings:\n \tsmtpAuth = OAUTHBEARER\n ----\n \n+Alternatively, you can use a tool developed by Google known as\n+https://github.com/google/gmail-oauth2-tools/tree/master/go/sendgmail[sendgmail]\n+to send emails using `git send-email`.\n+\n Use Microsoft Outlook as the SMTP Server\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.\n@@ -579,8 +583,7 @@ next time.\n \n If you are using OAuth2.0 authentication, you need to use an access token in\n place of a password when prompted. Various OAuth2.0 token generators are\n-available online. Community maintained credential helpers for Gmail and Outlook\n-are also available:\n+available online. Community maintained credential helpers are also available:\n \n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail]\n \t (cross platform, dedicated helper for authenticating Gmail accounts)\n@@ -588,6 +591,9 @@ are also available:\n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook]\n \t (cross platform, dedicated helper for authenticating Microsoft Outlook accounts)\n \n+\t- https://github.com/AdityaGarg8/git-credential-email[git-credential-yahoo]\n+\t (cross platform, dedicated helper for authenticating Yahoo accounts)\n+\n You can also see linkgit:gitcredentials[7] for more OAuth based authentication\n helpers.\n \n-- \n2.49.0\n\n"},{"id":"518352","messageId":"76AB293E-3A10-4827-92F2-852836E1F313@live.com","threadId":"63454","inReplyTo":"6D57A8EA-FDE8-42C9-9541-7B97C2DDBCA1@live.com","subject":"[PATCH v3 2/3] docs: improve formatting in git-send-email documentation","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-18T07:36:06Z","receivedAt":"2025-05-18T07:36:16Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"The current documentation for git-send-email had an inconsistent use of\n\"\", ``, and '' for quoting. This commit improves the formatting by\nusing the same style throughout the documentation.\n\nAlso, at some places, minor grammatical errors were fixed, and some\nnon existent links were removed.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/config/sendemail.adoc | 8 +-\n Documentation/git-send-email.adoc | 177 ++++++++++++++--------------\n 2 files changed, 94 insertions(+), 91 deletions(-)\n\ndiff --git a/Documentation/config/sendemail.adoc b/Documentation/config/sendemail.adoc\nindex 5ffcfc9f2a..0b1b2766f5 100644\n--- a/Documentation/config/sendemail.adoc\n+++ b/Documentation/config/sendemail.adoc\n@@ -19,9 +19,9 @@ sendemail..*::\n \t`sendemail.identity`.\n \n sendemail.multiEdit::\n-\tIf true (default), a single editor instance will be spawned to edit\n+\tIf `true` (default), a single editor instance will be spawned to edit\n \tfiles you have to edit (patches when `--annotate` is used, and the\n-\tsummary when `--compose` is used). If false, files will be edited one\n+\tsummary when `--compose` is used). If `false`, files will be edited one\n \tafter the other, spawning a new editor each time.\n \n sendemail.confirm::\n@@ -101,7 +101,7 @@ sendemail.signedOffCc (deprecated)::\n \n sendemail.smtpBatchSize::\n \tNumber of messages to be sent per connection, after that a relogin\n-\twill happen. If the value is 0 or undefined, send all messages in\n+\twill happen. If the value is `0` or undefined, send all messages in\n \tone connection.\n \tSee also the `--batch-size` option of linkgit:git-send-email[1].\n \n@@ -111,5 +111,5 @@ sendemail.smtpReloginDelay::\n \n sendemail.forbidSendmailVariables::\n \tTo avoid common misconfiguration mistakes, linkgit:git-send-email[1]\n-\twill abort with a warning if any configuration options for \"sendmail\"\n+\twill abort with a warning if any configuration options for `sendmail`\n \texist. Set this variable to bypass the check.\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 81f8cbc6f3..cd52150afd 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -21,7 +21,7 @@ Takes the patches given on the command line and emails them out.\n Patches can be specified as files, directories (which will send all\n files in the directory), or directly as a revision list. In the\n last case, any format accepted by linkgit:git-format-patch[1] can\n-be passed to git send-email, as well as options understood by\n+be passed to `git send-email`, as well as options understood by\n linkgit:git-format-patch[1].\n \n The header of the email is configurable via command-line options. If not\n@@ -35,11 +35,11 @@ There are two formats accepted for patch files:\n This is what linkgit:git-format-patch[1] generates. Most headers and MIME\n formatting are ignored.\n \n-2. The original format used by Greg Kroah-Hartman's 'send_lots_of_email.pl'\n+2. The original format used by Greg Kroah-Hartman's `send_lots_of_email.pl`\n script\n +\n-This format expects the first line of the file to contain the \"Cc:\" value\n-and the \"Subject:\" of the message as the second line.\n+This format expects the first line of the file to contain the 'Cc:' value\n+and the 'Subject:' of the message as the second line.\n \n \n OPTIONS\n@@ -54,13 +54,13 @@ Composing\n \t`sendemail.multiEdit`.\n \n --bcc=
,...::\n-\tSpecify a \"Bcc:\" value for each email. Default is the value of\n+\tSpecify a 'Bcc:' value for each email. Default is the value of\n \t`sendemail.bcc`.\n +\n This option may be specified multiple times.\n \n --cc=
,...::\n-\tSpecify a starting \"Cc:\" value for each email.\n+\tSpecify a starting 'Cc:' value for each email.\n \tDefault is the value of `sendemail.cc`.\n +\n This option may be specified multiple times.\n@@ -69,14 +69,14 @@ This option may be specified multiple times.\n \tInvoke a text editor (see GIT_EDITOR in linkgit:git-var[1])\n \tto edit an introductory message for the patch series.\n +\n-When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n-Subject, Reply-To, and In-Reply-To headers specified in the message. If\n-the body of the message (what you type after the headers and a blank\n-line) only contains blank (or Git: prefixed) lines, the summary won't be\n+When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n+'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n+message. If the body of the message (what you type after the headers and a\n+blank line) only contains blank (or Git: prefixed) lines, the summary won't be\n sent, but the headers mentioned above will be used unless they are\n removed.\n +\n-Missing From or In-Reply-To headers will be prompted for.\n+Missing 'From' or 'In-Reply-To' headers will be prompted for.\n +\n See the CONFIGURATION section for `sendemail.multiEdit`.\n \n@@ -85,13 +85,13 @@ See the CONFIGURATION section for `sendemail.multiEdit`.\n \tthe value of the `sendemail.from` configuration option is used. If\n \tneither the command-line option nor `sendemail.from` are set, then the\n \tuser will be prompted for the value. The default for the prompt will be\n-\tthe value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not\n-\tset, as returned by \"git var -l\".\n+\tthe value of `GIT_AUTHOR_IDENT`, or `GIT_COMMITTER_IDENT` if that is not\n+\tset, as returned by `git var -l`.\n \n --reply-to=
::\n \tSpecify the address where replies from recipients should go to.\n \tUse this if replies to messages should go to another address than what\n-\tis specified with the --from parameter.\n+\tis specified with the `--from` parameter.\n \n --in-reply-to=::\n \tMake the first mail (or all the mails with `--no-thread`) appear as a\n@@ -112,14 +112,14 @@ illustration below where `[PATCH v2 0/3]` is in reply to `[PATCH 0/2]`:\n [PATCH v2 2/3] New tests\n [PATCH v2 3/3] Implementation\n +\n-Only necessary if --compose is also set. If --compose\n+Only necessary if `--compose` is also set. If `--compose`\n is not set, this will be prompted for.\n \n --[no-]outlook-id-fix::\n \tMicrosoft Outlook SMTP servers discard the Message-ID sent via email and\n \tassign a new random Message-ID, thus breaking threads.\n +\n-With `--outlook-id-fix`, 'git send-email' uses a mechanism specific to\n+With `--outlook-id-fix`, `git send-email` uses a mechanism specific to\n Outlook servers to learn the Message-ID the server assigned to fix the\n threading. Use it only when you know that the server reports the\n rewritten Message-ID the same way as Outlook servers do.\n@@ -130,14 +130,14 @@ to 'smtp.office365.com' or 'smtp-mail.outlook.com'. Use\n \n --subject=::\n \tSpecify the initial subject of the email thread.\n-\tOnly necessary if --compose is also set. If --compose\n+\tOnly necessary if `--compose` is also set. If `--compose`\n \tis not set, this will be prompted for.\n \n --to=
,...::\n \tSpecify the primary recipient of the emails generated. Generally, this\n \twill be the upstream maintainer of the project involved. Default is the\n \tvalue of the `sendemail.to` configuration value; if that is unspecified,\n-\tand --to-cmd is not specified, this will be prompted for.\n+\tand `--to-cmd` is not specified, this will be prompted for.\n +\n This option may be specified multiple times.\n \n@@ -145,30 +145,30 @@ This option may be specified multiple times.\n \tWhen encountering a non-ASCII message or subject that does not\n \tdeclare its encoding, add headers/quoting to indicate it is\n \tencoded in . Default is the value of the\n-\t'sendemail.assume8bitEncoding'; if that is unspecified, this\n+\t`sendemail.assume8bitEncoding`; if that is unspecified, this\n \twill be prompted for if any non-ASCII files are encountered.\n +\n Note that no attempts whatsoever are made to validate the encoding.\n \n --compose-encoding=::\n \tSpecify encoding of compose message. Default is the value of the\n-\t'sendemail.composeEncoding'; if that is unspecified, UTF-8 is assumed.\n+\t`sendemail.composeEncoding`; if that is unspecified, UTF-8 is assumed.\n \n --transfer-encoding=(7bit|8bit|quoted-printable|base64|auto)::\n \tSpecify the transfer encoding to be used to send the message over SMTP.\n-\t7bit will fail upon encountering a non-ASCII message. quoted-printable\n+\t'7bit' will fail upon encountering a non-ASCII message. 'quoted-printable'\n \tcan be useful when the repository contains files that contain carriage\n-\treturns, but makes the raw patch email file (as saved from a MUA) much\n-\tharder to inspect manually. base64 is even more fool proof, but also\n-\teven more opaque. auto will use 8bit when possible, and quoted-printable\n-\totherwise.\n+\treturns, but makes the raw patch email file (as saved from an MUA) much\n+\tharder to inspect manually. 'base64' is even more fool proof, but also\n+\teven more opaque. 'auto' will use '8bit' when possible, and\n+\t'quoted-printable' otherwise.\n +\n Default is the value of the `sendemail.transferEncoding` configuration\n-value; if that is unspecified, default to `auto`.\n+value; if that is unspecified, default to 'auto'.\n \n --xmailer::\n --no-xmailer::\n-\tAdd (or prevent adding) the \"X-Mailer:\" header. By default,\n+\tAdd (or prevent adding) the 'X-Mailer:' header. By default,\n \tthe header is added, but it can be turned off by setting the\n \t`sendemail.xmailer` configuration variable to `false`.\n \n@@ -179,8 +179,8 @@ Sending\n \tSpecify the envelope sender used to send the emails.\n \tThis is useful if your default address is not the address that is\n \tsubscribed to a list. In order to use the 'From' address, set the\n-\tvalue to \"auto\". If you use the sendmail binary, you must have\n-\tsuitable privileges for the -f parameter. Default is the value of the\n+\tvalue to `auto`. If you use the `sendmail` binary, you must have\n+\tsuitable privileges for the `-f` parameter. Default is the value of the\n \t`sendemail.envelopeSender` configuration variable; if that is\n \tunspecified, choosing the envelope sender is left to your MTA.\n \n@@ -189,8 +189,8 @@ Sending\n \tbe sendmail-like; specifically, it must support the `-i` option.\n \tThe command will be executed in the shell if necessary. Default\n \tis the value of `sendemail.sendmailCmd`. If unspecified, and if\n-\t--smtp-server is also unspecified, git-send-email will search\n-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH.\n+\t`--smtp-server` is also unspecified, `git send-email` will search\n+\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH`.\n \n --smtp-encryption=::\n \tSpecify in what way encrypting begins for the SMTP connection.\n@@ -209,7 +209,7 @@ Sending\n --smtp-domain=::\n \tSpecifies the Fully Qualified Domain Name (FQDN) used in the\n \tHELO/EHLO command to the SMTP server. Some servers require the\n-\tFQDN to match your IP address. If not set, git send-email attempts\n+\tFQDN to match your IP address. If not set, `git send-email` attempts\n \tto determine your FQDN automatically. Default is the value of\n \t`sendemail.smtpDomain`.\n \n@@ -223,10 +223,10 @@ $ git send-email --smtp-auth=\"PLAIN LOGIN GSSAPI\" ...\n +\n If at least one of the specified mechanisms matches the ones advertised by the\n SMTP server and if it is supported by the utilized SASL library, the mechanism\n-is used for authentication. If neither 'sendemail.smtpAuth' nor `--smtp-auth`\n+is used for authentication. If neither `sendemail.smtpAuth` nor `--smtp-auth`\n is specified, all mechanisms supported by the SASL library can be used. The\n-special value 'none' maybe specified to completely disable authentication\n-independently of `--smtp-user`\n+special value `none` maybe specified to completely disable authentication\n+independently of `--smtp-user`.\n \n --smtp-pass[=]::\n \tPassword for SMTP-AUTH. The argument is optional: If no\n@@ -238,16 +238,16 @@ Furthermore, passwords need not be specified in configuration files\n or on the command line. If a username has been specified (with\n `--smtp-user` or a `sendemail.smtpUser`), but no password has been\n specified (with `--smtp-pass` or `sendemail.smtpPass`), then\n-a password is obtained using 'git-credential'.\n+a password is obtained using linkgit:git-credential[1].\n \n --no-smtp-auth::\n-\tDisable SMTP authentication. Short hand for `--smtp-auth=none`\n+\tDisable SMTP authentication. Short hand for `--smtp-auth=none`.\n \n --smtp-server=::\n \tIf set, specifies the outgoing SMTP server to use (e.g.\n \t`smtp.example.com` or a raw IP address). If unspecified, and if\n \t`--sendmail-cmd` is also unspecified, the default is to search\n-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH if such a\n+\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH` if such a\n \tprogram is available, falling back to `localhost` otherwise.\n +\n For backward compatibility, this option can also specify a full pathname\n@@ -260,7 +260,7 @@ instead.\n \tSpecifies a port different from the default port (SMTP\n \tservers typically listen to smtp port 25, but may also listen to\n \tsubmission port 587, or the common SSL smtp port 465);\n-\tsymbolic port names (e.g. \"submission\" instead of 587)\n+\tsymbolic port names (e.g. `submission` instead of 587)\n \tare also accepted. The port can also be set with the\n \t`sendemail.smtpServerPort` configuration variable.\n \n@@ -269,7 +269,7 @@ instead.\n \tDefault value can be specified by the `sendemail.smtpServerOption`\n \tconfiguration option.\n +\n-The --smtp-server-option option must be repeated for each option you want\n+The `--smtp-server-option` option must be repeated for each option you want\n to pass to the server. Likewise, different lines in the configuration files\n must be used for each option.\n \n@@ -279,9 +279,8 @@ must be used for each option.\n --smtp-ssl-cert-path::\n \tPath to a store of trusted CA certificates for SMTP SSL/TLS\n \tcertificate validation (either a directory that has been processed\n-\tby 'c_rehash', or a single file containing one or more PEM format\n-\tcertificates concatenated together: see verify(1) -CAfile and\n-\t-CApath for more information on these). Set it to an empty string\n+\tby `c_rehash`, or a single file containing one or more PEM format\n+\tcertificates concatenated together). Set it to an empty string\n \tto disable certificate verification. Defaults to the value of the\n \t`sendemail.smtpSSLCertPath` configuration variable, if set, or the\n \tbacking SSL library's compiled-in default otherwise (which should\n@@ -298,18 +297,18 @@ must be used for each option.\n \tconnection and authentication problems.\n \n --batch-size=::\n-\tSome email servers (e.g. smtp.163.com) limit the number emails to be\n+\tSome email servers (e.g. 'smtp.163.com') limit the number of emails to be\n \tsent per session (connection) and this will lead to a failure when\n \tsending many messages. With this option, send-email will disconnect after\n-\tsending $ messages and wait for a few seconds (see --relogin-delay)\n-\tand reconnect, to work around such a limit. You may want to\n-\tuse some form of credential helper to avoid having to retype\n-\tyour password every time this happens. Defaults to the\n+\tsending `$` messages and wait for a few seconds\n+\t(see `--relogin-delay`) and reconnect, to work around such a limit.\n+\tYou may want to use some form of credential helper to avoid having to\n+\tretype your password every time this happens. Defaults to the\n \t`sendemail.smtpBatchSize` configuration variable.\n \n --relogin-delay=::\n-\tWaiting $ seconds before reconnecting to SMTP server. Used together\n-\twith --batch-size option. Defaults to the `sendemail.smtpReloginDelay`\n+\tWaiting `$` seconds before reconnecting to SMTP server. Used together\n+\twith `--batch-size` option. Defaults to the `sendemail.smtpReloginDelay`\n \tconfiguration variable.\n \n Automating\n@@ -318,7 +317,7 @@ Automating\n --no-to::\n --no-cc::\n --no-bcc::\n-\tClears any list of \"To:\", \"Cc:\", \"Bcc:\" addresses previously\n+\tClears any list of 'To:', 'Cc:', 'Bcc:' addresses previously\n \tset via config.\n \n --no-identity::\n@@ -327,13 +326,13 @@ Automating\n \n --to-cmd=::\n \tSpecify a command to execute once per patch file which\n-\tshould generate patch file specific \"To:\" entries.\n+\tshould generate patch file specific 'To:' entries.\n \tOutput of this command must be single email address per line.\n-\tDefault is the value of 'sendemail.toCmd' configuration value.\n+\tDefault is the value of `sendemail.toCmd` configuration value.\n \n --cc-cmd=::\n \tSpecify a command to execute once per patch file which\n-\tshould generate patch file specific \"Cc:\" entries.\n+\tshould generate patch file specific 'Cc:' entries.\n \tOutput of this command must be single email address per line.\n \tDefault is the value of `sendemail.ccCmd` configuration value.\n \n@@ -341,7 +340,7 @@ Automating\n \tSpecify a command that is executed once per outgoing message\n \tand output RFC 2822 style header lines to be inserted into\n \tthem. When the `sendemail.headerCmd` configuration variable is\n-\tset, its value is always used. When --header-cmd is provided\n+\tset, its value is always used. When `--header-cmd` is provided\n \tat the command line, its value takes precedence over the\n \t`sendemail.headerCmd` configuration variable.\n \n@@ -350,7 +349,7 @@ Automating\n \n --[no-]chain-reply-to::\n \tIf this is set, each email will be sent as a reply to the previous\n-\temail sent. If disabled with \"--no-chain-reply-to\", all emails after\n+\temail sent. If disabled with `--no-chain-reply-to`, all emails after\n \tthe first will be sent as replies to the first email sent. When using\n \tthis, it is recommended that the first file given be an overview of the\n \tentire patch series. Disabled by default, but the `sendemail.chainReplyTo`\n@@ -363,21 +362,22 @@ Automating\n \tthe value of `sendemail.identity`.\n \n --[no-]signed-off-by-cc::\n-\tIf this is set, add emails found in the `Signed-off-by` trailer or Cc: lines to the\n-\tcc list. Default is the value of `sendemail.signedOffByCc` configuration\n-\tvalue; if that is unspecified, default to --signed-off-by-cc.\n+\tIf this is set, add emails found in the `Signed-off-by` trailer or 'Cc:'\n+\tlines to the cc list. Default is the value of `sendemail.signedOffByCc`\n+\tconfiguration value; if that is unspecified, default to\n+\t`--signed-off-by-cc`.\n \n --[no-]cc-cover::\n-\tIf this is set, emails found in Cc: headers in the first patch of\n+\tIf this is set, emails found in 'Cc:' headers in the first patch of\n \tthe series (typically the cover letter) are added to the cc list\n-\tfor each email set. Default is the value of 'sendemail.ccCover'\n-\tconfiguration value; if that is unspecified, default to --no-cc-cover.\n+\tfor each email set. Default is the value of `sendemail.ccCover`\n+\tconfiguration value; if that is unspecified, default to `--no-cc-cover`.\n \n --[no-]to-cover::\n-\tIf this is set, emails found in To: headers in the first patch of\n+\tIf this is set, emails found in 'To:' headers in the first patch of\n \tthe series (typically the cover letter) are added to the to list\n-\tfor each email set. Default is the value of 'sendemail.toCover'\n-\tconfiguration value; if that is unspecified, default to --no-to-cover.\n+\tfor each email set. Default is the value of `sendemail.toCover`\n+\tconfiguration value; if that is unspecified, default to `--no-to-cover`.\n \n --suppress-cc=::\n \tSpecify an additional category of recipients to suppress the\n@@ -401,36 +401,36 @@ Automating\n --\n +\n Default is the value of `sendemail.suppressCc` configuration value; if\n-that is unspecified, default to 'self' if --suppress-from is\n-specified, as well as 'body' if --no-signed-off-cc is specified.\n+that is unspecified, default to 'self' if `--suppress-from` is\n+specified, as well as 'body' if `--no-signed-off-cc` is specified.\n \n --[no-]suppress-from::\n-\tIf this is set, do not add the From: address to the cc: list.\n+\tIf this is set, do not add the 'From:' address to the 'Cc:' list.\n \tDefault is the value of `sendemail.suppressFrom` configuration\n-\tvalue; if that is unspecified, default to --no-suppress-from.\n+\tvalue; if that is unspecified, default to `--no-suppress-from`.\n \n --[no-]thread::\n-\tIf this is set, the In-Reply-To and References headers will be\n+\tIf this is set, the 'In-Reply-To' and 'References' headers will be\n \tadded to each email sent. Whether each mail refers to the\n-\tprevious email (`deep` threading per 'git format-patch'\n+\tprevious email (`deep` threading per `git format-patch`\n \twording) or to the first email (`shallow` threading) is\n-\tgoverned by \"--[no-]chain-reply-to\".\n+\tgoverned by `--[no-]chain-reply-to`.\n +\n-If disabled with \"--no-thread\", those headers will not be added\n-(unless specified with --in-reply-to). Default is the value of the\n+If disabled with `--no-thread`, those headers will not be added\n+(unless specified with `--in-reply-to`). Default is the value of the\n `sendemail.thread` configuration value; if that is unspecified,\n-default to --thread.\n+default to `--thread`.\n +\n It is up to the user to ensure that no In-Reply-To header already\n-exists when 'git send-email' is asked to add it (especially note that\n-'git format-patch' can be configured to do the threading itself).\n+exists when `git send-email` is asked to add it (especially note that\n+`git format-patch` can be configured to do the threading itself).\n Failure to do so may not produce the expected result in the\n recipient's MUA.\n \n --[no-]mailmap::\n \tUse the mailmap file (see linkgit:gitmailmap[5]) to map all\n \taddresses to their canonical real name and email address. Additional\n-\tmailmap data specific to git-send-email may be provided using the\n+\tmailmap data specific to `git send-email` may be provided using the\n \t`sendemail.mailmap.file` or `sendemail.mailmap.blob` configuration\n \tvalues. Defaults to `sendemail.mailmap`.\n \n@@ -441,12 +441,12 @@ Administering\n \tConfirm just before sending:\n +\n --\n-- 'always' will always confirm before sending\n-- 'never' will never confirm before sending\n+- 'always' will always confirm before sending.\n+- 'never' will never confirm before sending.\n - 'cc' will confirm before sending when send-email has automatically\n- added addresses from the patch to the Cc list\n+ added addresses from the patch to the Cc list.\n - 'compose' will confirm before sending the first message when using --compose.\n-- 'auto' is equivalent to 'cc' + 'compose'\n+- 'auto' is equivalent to 'cc' + 'compose'.\n --\n +\n Default is the value of `sendemail.confirm` configuration value; if that\n@@ -460,10 +460,10 @@ have been specified, in which case default to 'compose'.\n \tWhen an argument may be understood either as a reference or as a file name,\n \tchoose to understand it as a format-patch argument (`--format-patch`)\n \tor as a file name (`--no-format-patch`). By default, when such a conflict\n-\toccurs, git send-email will fail.\n+\toccurs, `git send-email` will fail.\n \n --quiet::\n-\tMake git-send-email less verbose. One line per email should be\n+\tMake `git send-email` less verbose. One line per email should be\n \tall that is output.\n \n --[no-]validate::\n@@ -525,7 +525,7 @@ edit `~/.gitconfig` to specify your account settings:\n ----\n \n If you have multi-factor authentication set up on your Gmail account, you can\n-generate an app-specific password for use with 'git send-email'. Visit\n+generate an app-specific password for use with `git send-email`. Visit\n https://security.google.com/settings/security/apppasswords to create it.\n \n You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n@@ -599,9 +599,12 @@ helpers.\n \n Note: the following core Perl modules that may be installed with your\n distribution of Perl are required:\n-MIME::Base64, MIME::QuotedPrint, Net::Domain and Net::SMTP.\n+\n+'MIME::Base64', 'MIME::QuotedPrint', 'Net::Domain' and 'Net::SMTP'.\n+\n These additional Perl modules are also required:\n-Authen::SASL and Mail::Address.\n+\n+'Authen::SASL' and 'Mail::Address'.\n \n \n SEE ALSO\n-- \n2.49.0\n\n"},{"id":"518353","messageId":"2D9CF051-5135-40FB-9C15-6E9E1173C9EC@live.com","threadId":"63454","inReplyTo":"6D57A8EA-FDE8-42C9-9541-7B97C2DDBCA1@live.com","subject":"[PATCH v3 3/3] docs: remove credential helper links for emails from gitcredentials","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-18T07:36:36Z","receivedAt":"2025-05-18T07:36:44Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"In a recent attempt to add links of email helpers to git-scm.com [1], I\ncame to a conclusion that the links in the gitcredentials page are meant\nfor people needing credential helpers for cloning, fetching and pushing\nrepositories to remote hosts, and not sending emails. gitcredentials\ndocs don't even talk about send emails, thus confirming this view.\n\nSo, lets remove these links from the gitcredentials page. The links are\nstill available in the git-send-email documentation, which is the right\nplace for them.\n\n[1]: https://github.com/git/git-scm.com/pull/2005\n\nSigned-off-by: Aditya Garg \n---\n Documentation/gitcredentials.adoc | 4 ----\n 1 file changed, 4 deletions(-)\n\ndiff --git a/Documentation/gitcredentials.adoc b/Documentation/gitcredentials.adoc\nindex b49923db02..3337bb475d 100644\n--- a/Documentation/gitcredentials.adoc\n+++ b/Documentation/gitcredentials.adoc\n@@ -133,10 +133,6 @@ Popular helpers with OAuth support include:\n \n - https://github.com/hickford/git-credential-oauth[git-credential-oauth] (cross platform, included in many Linux distributions)\n \n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail] (cross platform, dedicated helper to authenticate Gmail accounts for linkgit:git-send-email[1])\n-\n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook] (cross platform, dedicated helper to authenticate Microsoft Outlook accounts for linkgit:git-send-email[1])\n-\n CREDENTIAL CONTEXTS\n -------------------\n \n-- \n2.49.0\n\n"},{"id":"518404","messageId":"A84F634C-3423-48E2-B648-068A75423037@live.com","threadId":"63454","inReplyTo":"PN3PR01MB95971131BD3CD89771F19E5DB896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"[PATCH v4 0/3] docs: update email credential helpers and improve formatting","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-19T12:51:19Z","receivedAt":"2025-05-19T12:51:24Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"Hi all,\n\nThis patch series included three patches:\n\n1. The first patch adds a link to the `git-credential-yahoo` helper for\n Yahoo accounts and links Google's `sendgmail` tool as an alternative\n method for sending emails through Gmail.\n\n2. The second patch improves the formatting of the `git-send-email`\n documentation, making it more readable and consistent.\n\n3. The third patch removed the email credential helper links from the\n `gitcredentials` page. The links are still available in the\n `git-send-email` documentation, which is the right place for them.\n\nDetailed explanation of the changes has been done in individual patch.\n\nv2: Removed instructions for Yahoo SMTP server since I've realised that\n Yahoo *was* a popular email service. Also, the instructions were\n just making the docs more crowded. I've also added a link to\n Google's `sendgmail` tool in the first patch. The second patch has been\n added to address the issues that came up here:\n https://github.com/git/git-scm.com/pull/2005\n\nv3: Added a patch to improve the formatting of the `git-send-email`\n documentation.\n\nv4: Added cpan links of the perl modules requires for `git-send-email`\n to work.\n\nAditya Garg (3):\n docs: add credential helper for yahoo and link Google's sendgmail tool\n docs: improve formatting in git-send-email documentation\n docs: remove credential helper links for emails from gitcredentials\n\n Documentation/config/sendemail.adoc | 8 +-\n Documentation/git-send-email.adoc | 191 +++++++++++++++-------------\n Documentation/gitcredentials.adoc | 4 -\n 3 files changed, 106 insertions(+), 97 deletions(-)\n\n-- \n2.49.0\n\n"},{"id":"518405","messageId":"5DDE8CCF-790B-4E1F-A601-473436483D52@live.com","threadId":"63454","inReplyTo":"A84F634C-3423-48E2-B648-068A75423037@live.com","subject":"[PATCH v4 1/3] docs: add credential helper for yahoo and link Google's sendgmail tool","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-19T12:52:05Z","receivedAt":"2025-05-19T12:52:10Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"This commit links `git-credential-yahoo` as a credential helper for\nYahoo accounts. Also, Google's `sendgmail` tool has been linked as an\nalternative method for sending emails through Gmail.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/git-send-email.adoc | 10 ++++++++--\n 1 file changed, 8 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 26fda63c2f..81f8cbc6f3 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -543,6 +543,10 @@ settings:\n \tsmtpAuth = OAUTHBEARER\n ----\n \n+Alternatively, you can use a tool developed by Google known as\n+https://github.com/google/gmail-oauth2-tools/tree/master/go/sendgmail[sendgmail]\n+to send emails using `git send-email`.\n+\n Use Microsoft Outlook as the SMTP Server\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.\n@@ -579,8 +583,7 @@ next time.\n \n If you are using OAuth2.0 authentication, you need to use an access token in\n place of a password when prompted. Various OAuth2.0 token generators are\n-available online. Community maintained credential helpers for Gmail and Outlook\n-are also available:\n+available online. Community maintained credential helpers are also available:\n \n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail]\n \t (cross platform, dedicated helper for authenticating Gmail accounts)\n@@ -588,6 +591,9 @@ are also available:\n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook]\n \t (cross platform, dedicated helper for authenticating Microsoft Outlook accounts)\n \n+\t- https://github.com/AdityaGarg8/git-credential-email[git-credential-yahoo]\n+\t (cross platform, dedicated helper for authenticating Yahoo accounts)\n+\n You can also see linkgit:gitcredentials[7] for more OAuth based authentication\n helpers.\n \n-- \n2.49.0\n\n"},{"id":"518406","messageId":"4AD5E37D-323C-4AD1-89AF-1FF7A8F6EAE3@live.com","threadId":"63454","inReplyTo":"A84F634C-3423-48E2-B648-068A75423037@live.com","subject":"[PATCH v4 2/3] docs: improve formatting in git-send-email documentation","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-19T12:52:38Z","receivedAt":"2025-05-19T12:52:43Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"The current documentation for git-send-email had an inconsistent use of\n\"\", ``, and '' for quoting. This commit improves the formatting by\nusing the same style throughout the documentation.\n\nAlso, at some places, minor grammatical errors were fixed, and some\nnon existent links were removed.\n\nFinally, the cpan links of necessary perl modules have been added to\nmake their installation easier.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/config/sendemail.adoc | 8 +-\n Documentation/git-send-email.adoc | 181 +++++++++++++++-------------\n 2 files changed, 98 insertions(+), 91 deletions(-)\n\ndiff --git a/Documentation/config/sendemail.adoc b/Documentation/config/sendemail.adoc\nindex 5ffcfc9f2a..0b1b2766f5 100644\n--- a/Documentation/config/sendemail.adoc\n+++ b/Documentation/config/sendemail.adoc\n@@ -19,9 +19,9 @@ sendemail..*::\n \t`sendemail.identity`.\n \n sendemail.multiEdit::\n-\tIf true (default), a single editor instance will be spawned to edit\n+\tIf `true` (default), a single editor instance will be spawned to edit\n \tfiles you have to edit (patches when `--annotate` is used, and the\n-\tsummary when `--compose` is used). If false, files will be edited one\n+\tsummary when `--compose` is used). If `false`, files will be edited one\n \tafter the other, spawning a new editor each time.\n \n sendemail.confirm::\n@@ -101,7 +101,7 @@ sendemail.signedOffCc (deprecated)::\n \n sendemail.smtpBatchSize::\n \tNumber of messages to be sent per connection, after that a relogin\n-\twill happen. If the value is 0 or undefined, send all messages in\n+\twill happen. If the value is `0` or undefined, send all messages in\n \tone connection.\n \tSee also the `--batch-size` option of linkgit:git-send-email[1].\n \n@@ -111,5 +111,5 @@ sendemail.smtpReloginDelay::\n \n sendemail.forbidSendmailVariables::\n \tTo avoid common misconfiguration mistakes, linkgit:git-send-email[1]\n-\twill abort with a warning if any configuration options for \"sendmail\"\n+\twill abort with a warning if any configuration options for `sendmail`\n \texist. Set this variable to bypass the check.\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 81f8cbc6f3..aff0861d29 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -21,7 +21,7 @@ Takes the patches given on the command line and emails them out.\n Patches can be specified as files, directories (which will send all\n files in the directory), or directly as a revision list. In the\n last case, any format accepted by linkgit:git-format-patch[1] can\n-be passed to git send-email, as well as options understood by\n+be passed to `git send-email`, as well as options understood by\n linkgit:git-format-patch[1].\n \n The header of the email is configurable via command-line options. If not\n@@ -35,11 +35,11 @@ There are two formats accepted for patch files:\n This is what linkgit:git-format-patch[1] generates. Most headers and MIME\n formatting are ignored.\n \n-2. The original format used by Greg Kroah-Hartman's 'send_lots_of_email.pl'\n+2. The original format used by Greg Kroah-Hartman's `send_lots_of_email.pl`\n script\n +\n-This format expects the first line of the file to contain the \"Cc:\" value\n-and the \"Subject:\" of the message as the second line.\n+This format expects the first line of the file to contain the 'Cc:' value\n+and the 'Subject:' of the message as the second line.\n \n \n OPTIONS\n@@ -54,13 +54,13 @@ Composing\n \t`sendemail.multiEdit`.\n \n --bcc=
,...::\n-\tSpecify a \"Bcc:\" value for each email. Default is the value of\n+\tSpecify a 'Bcc:' value for each email. Default is the value of\n \t`sendemail.bcc`.\n +\n This option may be specified multiple times.\n \n --cc=
,...::\n-\tSpecify a starting \"Cc:\" value for each email.\n+\tSpecify a starting 'Cc:' value for each email.\n \tDefault is the value of `sendemail.cc`.\n +\n This option may be specified multiple times.\n@@ -69,14 +69,14 @@ This option may be specified multiple times.\n \tInvoke a text editor (see GIT_EDITOR in linkgit:git-var[1])\n \tto edit an introductory message for the patch series.\n +\n-When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n-Subject, Reply-To, and In-Reply-To headers specified in the message. If\n-the body of the message (what you type after the headers and a blank\n-line) only contains blank (or Git: prefixed) lines, the summary won't be\n+When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n+'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n+message. If the body of the message (what you type after the headers and a\n+blank line) only contains blank (or Git: prefixed) lines, the summary won't be\n sent, but the headers mentioned above will be used unless they are\n removed.\n +\n-Missing From or In-Reply-To headers will be prompted for.\n+Missing 'From' or 'In-Reply-To' headers will be prompted for.\n +\n See the CONFIGURATION section for `sendemail.multiEdit`.\n \n@@ -85,13 +85,13 @@ See the CONFIGURATION section for `sendemail.multiEdit`.\n \tthe value of the `sendemail.from` configuration option is used. If\n \tneither the command-line option nor `sendemail.from` are set, then the\n \tuser will be prompted for the value. The default for the prompt will be\n-\tthe value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not\n-\tset, as returned by \"git var -l\".\n+\tthe value of `GIT_AUTHOR_IDENT`, or `GIT_COMMITTER_IDENT` if that is not\n+\tset, as returned by `git var -l`.\n \n --reply-to=
::\n \tSpecify the address where replies from recipients should go to.\n \tUse this if replies to messages should go to another address than what\n-\tis specified with the --from parameter.\n+\tis specified with the `--from` parameter.\n \n --in-reply-to=::\n \tMake the first mail (or all the mails with `--no-thread`) appear as a\n@@ -112,14 +112,14 @@ illustration below where `[PATCH v2 0/3]` is in reply to `[PATCH 0/2]`:\n [PATCH v2 2/3] New tests\n [PATCH v2 3/3] Implementation\n +\n-Only necessary if --compose is also set. If --compose\n+Only necessary if `--compose` is also set. If `--compose`\n is not set, this will be prompted for.\n \n --[no-]outlook-id-fix::\n \tMicrosoft Outlook SMTP servers discard the Message-ID sent via email and\n \tassign a new random Message-ID, thus breaking threads.\n +\n-With `--outlook-id-fix`, 'git send-email' uses a mechanism specific to\n+With `--outlook-id-fix`, `git send-email` uses a mechanism specific to\n Outlook servers to learn the Message-ID the server assigned to fix the\n threading. Use it only when you know that the server reports the\n rewritten Message-ID the same way as Outlook servers do.\n@@ -130,14 +130,14 @@ to 'smtp.office365.com' or 'smtp-mail.outlook.com'. Use\n \n --subject=::\n \tSpecify the initial subject of the email thread.\n-\tOnly necessary if --compose is also set. If --compose\n+\tOnly necessary if `--compose` is also set. If `--compose`\n \tis not set, this will be prompted for.\n \n --to=
,...::\n \tSpecify the primary recipient of the emails generated. Generally, this\n \twill be the upstream maintainer of the project involved. Default is the\n \tvalue of the `sendemail.to` configuration value; if that is unspecified,\n-\tand --to-cmd is not specified, this will be prompted for.\n+\tand `--to-cmd` is not specified, this will be prompted for.\n +\n This option may be specified multiple times.\n \n@@ -145,30 +145,30 @@ This option may be specified multiple times.\n \tWhen encountering a non-ASCII message or subject that does not\n \tdeclare its encoding, add headers/quoting to indicate it is\n \tencoded in . Default is the value of the\n-\t'sendemail.assume8bitEncoding'; if that is unspecified, this\n+\t`sendemail.assume8bitEncoding`; if that is unspecified, this\n \twill be prompted for if any non-ASCII files are encountered.\n +\n Note that no attempts whatsoever are made to validate the encoding.\n \n --compose-encoding=::\n \tSpecify encoding of compose message. Default is the value of the\n-\t'sendemail.composeEncoding'; if that is unspecified, UTF-8 is assumed.\n+\t`sendemail.composeEncoding`; if that is unspecified, UTF-8 is assumed.\n \n --transfer-encoding=(7bit|8bit|quoted-printable|base64|auto)::\n \tSpecify the transfer encoding to be used to send the message over SMTP.\n-\t7bit will fail upon encountering a non-ASCII message. quoted-printable\n+\t'7bit' will fail upon encountering a non-ASCII message. 'quoted-printable'\n \tcan be useful when the repository contains files that contain carriage\n-\treturns, but makes the raw patch email file (as saved from a MUA) much\n-\tharder to inspect manually. base64 is even more fool proof, but also\n-\teven more opaque. auto will use 8bit when possible, and quoted-printable\n-\totherwise.\n+\treturns, but makes the raw patch email file (as saved from an MUA) much\n+\tharder to inspect manually. 'base64' is even more fool proof, but also\n+\teven more opaque. 'auto' will use '8bit' when possible, and\n+\t'quoted-printable' otherwise.\n +\n Default is the value of the `sendemail.transferEncoding` configuration\n-value; if that is unspecified, default to `auto`.\n+value; if that is unspecified, default to 'auto'.\n \n --xmailer::\n --no-xmailer::\n-\tAdd (or prevent adding) the \"X-Mailer:\" header. By default,\n+\tAdd (or prevent adding) the 'X-Mailer:' header. By default,\n \tthe header is added, but it can be turned off by setting the\n \t`sendemail.xmailer` configuration variable to `false`.\n \n@@ -179,8 +179,8 @@ Sending\n \tSpecify the envelope sender used to send the emails.\n \tThis is useful if your default address is not the address that is\n \tsubscribed to a list. In order to use the 'From' address, set the\n-\tvalue to \"auto\". If you use the sendmail binary, you must have\n-\tsuitable privileges for the -f parameter. Default is the value of the\n+\tvalue to `auto`. If you use the `sendmail` binary, you must have\n+\tsuitable privileges for the `-f` parameter. Default is the value of the\n \t`sendemail.envelopeSender` configuration variable; if that is\n \tunspecified, choosing the envelope sender is left to your MTA.\n \n@@ -189,8 +189,8 @@ Sending\n \tbe sendmail-like; specifically, it must support the `-i` option.\n \tThe command will be executed in the shell if necessary. Default\n \tis the value of `sendemail.sendmailCmd`. If unspecified, and if\n-\t--smtp-server is also unspecified, git-send-email will search\n-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH.\n+\t`--smtp-server` is also unspecified, `git send-email` will search\n+\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH`.\n \n --smtp-encryption=::\n \tSpecify in what way encrypting begins for the SMTP connection.\n@@ -209,7 +209,7 @@ Sending\n --smtp-domain=::\n \tSpecifies the Fully Qualified Domain Name (FQDN) used in the\n \tHELO/EHLO command to the SMTP server. Some servers require the\n-\tFQDN to match your IP address. If not set, git send-email attempts\n+\tFQDN to match your IP address. If not set, `git send-email` attempts\n \tto determine your FQDN automatically. Default is the value of\n \t`sendemail.smtpDomain`.\n \n@@ -223,10 +223,10 @@ $ git send-email --smtp-auth=\"PLAIN LOGIN GSSAPI\" ...\n +\n If at least one of the specified mechanisms matches the ones advertised by the\n SMTP server and if it is supported by the utilized SASL library, the mechanism\n-is used for authentication. If neither 'sendemail.smtpAuth' nor `--smtp-auth`\n+is used for authentication. If neither `sendemail.smtpAuth` nor `--smtp-auth`\n is specified, all mechanisms supported by the SASL library can be used. The\n-special value 'none' maybe specified to completely disable authentication\n-independently of `--smtp-user`\n+special value `none` maybe specified to completely disable authentication\n+independently of `--smtp-user`.\n \n --smtp-pass[=]::\n \tPassword for SMTP-AUTH. The argument is optional: If no\n@@ -238,16 +238,16 @@ Furthermore, passwords need not be specified in configuration files\n or on the command line. If a username has been specified (with\n `--smtp-user` or a `sendemail.smtpUser`), but no password has been\n specified (with `--smtp-pass` or `sendemail.smtpPass`), then\n-a password is obtained using 'git-credential'.\n+a password is obtained using linkgit:git-credential[1].\n \n --no-smtp-auth::\n-\tDisable SMTP authentication. Short hand for `--smtp-auth=none`\n+\tDisable SMTP authentication. Short hand for `--smtp-auth=none`.\n \n --smtp-server=::\n \tIf set, specifies the outgoing SMTP server to use (e.g.\n \t`smtp.example.com` or a raw IP address). If unspecified, and if\n \t`--sendmail-cmd` is also unspecified, the default is to search\n-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH if such a\n+\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH` if such a\n \tprogram is available, falling back to `localhost` otherwise.\n +\n For backward compatibility, this option can also specify a full pathname\n@@ -260,7 +260,7 @@ instead.\n \tSpecifies a port different from the default port (SMTP\n \tservers typically listen to smtp port 25, but may also listen to\n \tsubmission port 587, or the common SSL smtp port 465);\n-\tsymbolic port names (e.g. \"submission\" instead of 587)\n+\tsymbolic port names (e.g. `submission` instead of 587)\n \tare also accepted. The port can also be set with the\n \t`sendemail.smtpServerPort` configuration variable.\n \n@@ -269,7 +269,7 @@ instead.\n \tDefault value can be specified by the `sendemail.smtpServerOption`\n \tconfiguration option.\n +\n-The --smtp-server-option option must be repeated for each option you want\n+The `--smtp-server-option` option must be repeated for each option you want\n to pass to the server. Likewise, different lines in the configuration files\n must be used for each option.\n \n@@ -279,9 +279,8 @@ must be used for each option.\n --smtp-ssl-cert-path::\n \tPath to a store of trusted CA certificates for SMTP SSL/TLS\n \tcertificate validation (either a directory that has been processed\n-\tby 'c_rehash', or a single file containing one or more PEM format\n-\tcertificates concatenated together: see verify(1) -CAfile and\n-\t-CApath for more information on these). Set it to an empty string\n+\tby `c_rehash`, or a single file containing one or more PEM format\n+\tcertificates concatenated together). Set it to an empty string\n \tto disable certificate verification. Defaults to the value of the\n \t`sendemail.smtpSSLCertPath` configuration variable, if set, or the\n \tbacking SSL library's compiled-in default otherwise (which should\n@@ -298,18 +297,18 @@ must be used for each option.\n \tconnection and authentication problems.\n \n --batch-size=::\n-\tSome email servers (e.g. smtp.163.com) limit the number emails to be\n+\tSome email servers (e.g. 'smtp.163.com') limit the number of emails to be\n \tsent per session (connection) and this will lead to a failure when\n \tsending many messages. With this option, send-email will disconnect after\n-\tsending $ messages and wait for a few seconds (see --relogin-delay)\n-\tand reconnect, to work around such a limit. You may want to\n-\tuse some form of credential helper to avoid having to retype\n-\tyour password every time this happens. Defaults to the\n+\tsending `$` messages and wait for a few seconds\n+\t(see `--relogin-delay`) and reconnect, to work around such a limit.\n+\tYou may want to use some form of credential helper to avoid having to\n+\tretype your password every time this happens. Defaults to the\n \t`sendemail.smtpBatchSize` configuration variable.\n \n --relogin-delay=::\n-\tWaiting $ seconds before reconnecting to SMTP server. Used together\n-\twith --batch-size option. Defaults to the `sendemail.smtpReloginDelay`\n+\tWaiting `$` seconds before reconnecting to SMTP server. Used together\n+\twith `--batch-size` option. Defaults to the `sendemail.smtpReloginDelay`\n \tconfiguration variable.\n \n Automating\n@@ -318,7 +317,7 @@ Automating\n --no-to::\n --no-cc::\n --no-bcc::\n-\tClears any list of \"To:\", \"Cc:\", \"Bcc:\" addresses previously\n+\tClears any list of 'To:', 'Cc:', 'Bcc:' addresses previously\n \tset via config.\n \n --no-identity::\n@@ -327,13 +326,13 @@ Automating\n \n --to-cmd=::\n \tSpecify a command to execute once per patch file which\n-\tshould generate patch file specific \"To:\" entries.\n+\tshould generate patch file specific 'To:' entries.\n \tOutput of this command must be single email address per line.\n-\tDefault is the value of 'sendemail.toCmd' configuration value.\n+\tDefault is the value of `sendemail.toCmd` configuration value.\n \n --cc-cmd=::\n \tSpecify a command to execute once per patch file which\n-\tshould generate patch file specific \"Cc:\" entries.\n+\tshould generate patch file specific 'Cc:' entries.\n \tOutput of this command must be single email address per line.\n \tDefault is the value of `sendemail.ccCmd` configuration value.\n \n@@ -341,7 +340,7 @@ Automating\n \tSpecify a command that is executed once per outgoing message\n \tand output RFC 2822 style header lines to be inserted into\n \tthem. When the `sendemail.headerCmd` configuration variable is\n-\tset, its value is always used. When --header-cmd is provided\n+\tset, its value is always used. When `--header-cmd` is provided\n \tat the command line, its value takes precedence over the\n \t`sendemail.headerCmd` configuration variable.\n \n@@ -350,7 +349,7 @@ Automating\n \n --[no-]chain-reply-to::\n \tIf this is set, each email will be sent as a reply to the previous\n-\temail sent. If disabled with \"--no-chain-reply-to\", all emails after\n+\temail sent. If disabled with `--no-chain-reply-to`, all emails after\n \tthe first will be sent as replies to the first email sent. When using\n \tthis, it is recommended that the first file given be an overview of the\n \tentire patch series. Disabled by default, but the `sendemail.chainReplyTo`\n@@ -363,21 +362,22 @@ Automating\n \tthe value of `sendemail.identity`.\n \n --[no-]signed-off-by-cc::\n-\tIf this is set, add emails found in the `Signed-off-by` trailer or Cc: lines to the\n-\tcc list. Default is the value of `sendemail.signedOffByCc` configuration\n-\tvalue; if that is unspecified, default to --signed-off-by-cc.\n+\tIf this is set, add emails found in the `Signed-off-by` trailer or 'Cc:'\n+\tlines to the cc list. Default is the value of `sendemail.signedOffByCc`\n+\tconfiguration value; if that is unspecified, default to\n+\t`--signed-off-by-cc`.\n \n --[no-]cc-cover::\n-\tIf this is set, emails found in Cc: headers in the first patch of\n+\tIf this is set, emails found in 'Cc:' headers in the first patch of\n \tthe series (typically the cover letter) are added to the cc list\n-\tfor each email set. Default is the value of 'sendemail.ccCover'\n-\tconfiguration value; if that is unspecified, default to --no-cc-cover.\n+\tfor each email set. Default is the value of `sendemail.ccCover`\n+\tconfiguration value; if that is unspecified, default to `--no-cc-cover`.\n \n --[no-]to-cover::\n-\tIf this is set, emails found in To: headers in the first patch of\n+\tIf this is set, emails found in 'To:' headers in the first patch of\n \tthe series (typically the cover letter) are added to the to list\n-\tfor each email set. Default is the value of 'sendemail.toCover'\n-\tconfiguration value; if that is unspecified, default to --no-to-cover.\n+\tfor each email set. Default is the value of `sendemail.toCover`\n+\tconfiguration value; if that is unspecified, default to `--no-to-cover`.\n \n --suppress-cc=::\n \tSpecify an additional category of recipients to suppress the\n@@ -401,36 +401,36 @@ Automating\n --\n +\n Default is the value of `sendemail.suppressCc` configuration value; if\n-that is unspecified, default to 'self' if --suppress-from is\n-specified, as well as 'body' if --no-signed-off-cc is specified.\n+that is unspecified, default to 'self' if `--suppress-from` is\n+specified, as well as 'body' if `--no-signed-off-cc` is specified.\n \n --[no-]suppress-from::\n-\tIf this is set, do not add the From: address to the cc: list.\n+\tIf this is set, do not add the 'From:' address to the 'Cc:' list.\n \tDefault is the value of `sendemail.suppressFrom` configuration\n-\tvalue; if that is unspecified, default to --no-suppress-from.\n+\tvalue; if that is unspecified, default to `--no-suppress-from`.\n \n --[no-]thread::\n-\tIf this is set, the In-Reply-To and References headers will be\n+\tIf this is set, the 'In-Reply-To' and 'References' headers will be\n \tadded to each email sent. Whether each mail refers to the\n-\tprevious email (`deep` threading per 'git format-patch'\n+\tprevious email (`deep` threading per `git format-patch`\n \twording) or to the first email (`shallow` threading) is\n-\tgoverned by \"--[no-]chain-reply-to\".\n+\tgoverned by `--[no-]chain-reply-to`.\n +\n-If disabled with \"--no-thread\", those headers will not be added\n-(unless specified with --in-reply-to). Default is the value of the\n+If disabled with `--no-thread`, those headers will not be added\n+(unless specified with `--in-reply-to`). Default is the value of the\n `sendemail.thread` configuration value; if that is unspecified,\n-default to --thread.\n+default to `--thread`.\n +\n It is up to the user to ensure that no In-Reply-To header already\n-exists when 'git send-email' is asked to add it (especially note that\n-'git format-patch' can be configured to do the threading itself).\n+exists when `git send-email` is asked to add it (especially note that\n+`git format-patch` can be configured to do the threading itself).\n Failure to do so may not produce the expected result in the\n recipient's MUA.\n \n --[no-]mailmap::\n \tUse the mailmap file (see linkgit:gitmailmap[5]) to map all\n \taddresses to their canonical real name and email address. Additional\n-\tmailmap data specific to git-send-email may be provided using the\n+\tmailmap data specific to `git send-email` may be provided using the\n \t`sendemail.mailmap.file` or `sendemail.mailmap.blob` configuration\n \tvalues. Defaults to `sendemail.mailmap`.\n \n@@ -441,12 +441,12 @@ Administering\n \tConfirm just before sending:\n +\n --\n-- 'always' will always confirm before sending\n-- 'never' will never confirm before sending\n+- 'always' will always confirm before sending.\n+- 'never' will never confirm before sending.\n - 'cc' will confirm before sending when send-email has automatically\n- added addresses from the patch to the Cc list\n+ added addresses from the patch to the Cc list.\n - 'compose' will confirm before sending the first message when using --compose.\n-- 'auto' is equivalent to 'cc' + 'compose'\n+- 'auto' is equivalent to 'cc' + 'compose'.\n --\n +\n Default is the value of `sendemail.confirm` configuration value; if that\n@@ -460,10 +460,10 @@ have been specified, in which case default to 'compose'.\n \tWhen an argument may be understood either as a reference or as a file name,\n \tchoose to understand it as a format-patch argument (`--format-patch`)\n \tor as a file name (`--no-format-patch`). By default, when such a conflict\n-\toccurs, git send-email will fail.\n+\toccurs, `git send-email` will fail.\n \n --quiet::\n-\tMake git-send-email less verbose. One line per email should be\n+\tMake `git send-email` less verbose. One line per email should be\n \tall that is output.\n \n --[no-]validate::\n@@ -525,7 +525,7 @@ edit `~/.gitconfig` to specify your account settings:\n ----\n \n If you have multi-factor authentication set up on your Gmail account, you can\n-generate an app-specific password for use with 'git send-email'. Visit\n+generate an app-specific password for use with `git send-email`. Visit\n https://security.google.com/settings/security/apppasswords to create it.\n \n You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n@@ -599,9 +599,16 @@ helpers.\n \n Note: the following core Perl modules that may be installed with your\n distribution of Perl are required:\n-MIME::Base64, MIME::QuotedPrint, Net::Domain and Net::SMTP.\n+\n+https://metacpan.org/pod/MIME::Base64[MIME::Base64],\n+https://metacpan.org/pod/MIME::QuotedPrint[MIME::QuotedPrint],\n+https://metacpan.org/pod/Net::Domain[Net::Domain] and\n+https://metacpan.org/pod/Net::SMTP[Net::SMTP].\n+\n These additional Perl modules are also required:\n-Authen::SASL and Mail::Address.\n+\n+https://metacpan.org/pod/Authen::SASL[Authen::SASL] and\n+https://metacpan.org/pod/Mail::Address[Mail::Address].\n \n \n SEE ALSO\n-- \n2.49.0\n\n"},{"id":"518407","messageId":"E988D11E-04BC-4126-A1EE-B64F79412161@live.com","threadId":"63454","inReplyTo":"A84F634C-3423-48E2-B648-068A75423037@live.com","subject":"[PATCH v4 3/3] docs: remove credential helper links for emails from gitcredentials","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-19T12:53:12Z","receivedAt":"2025-05-19T12:53:16Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"In a recent attempt to add links of email helpers to git-scm.com [1], I\ncame to a conclusion that the links in the gitcredentials page are meant\nfor people needing credential helpers for cloning, fetching and pushing\nrepositories to remote hosts, and not sending emails. gitcredentials\ndocs don't even talk about send emails, thus confirming this view.\n\nSo, lets remove these links from the gitcredentials page. The links are\nstill available in the git-send-email documentation, which is the right\nplace for them.\n\n[1]: https://github.com/git/git-scm.com/pull/2005\n\nSigned-off-by: Aditya Garg \n---\n Documentation/gitcredentials.adoc | 4 ----\n 1 file changed, 4 deletions(-)\n\ndiff --git a/Documentation/gitcredentials.adoc b/Documentation/gitcredentials.adoc\nindex b49923db02..3337bb475d 100644\n--- a/Documentation/gitcredentials.adoc\n+++ b/Documentation/gitcredentials.adoc\n@@ -133,10 +133,6 @@ Popular helpers with OAuth support include:\n \n - https://github.com/hickford/git-credential-oauth[git-credential-oauth] (cross platform, included in many Linux distributions)\n \n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail] (cross platform, dedicated helper to authenticate Gmail accounts for linkgit:git-send-email[1])\n-\n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook] (cross platform, dedicated helper to authenticate Microsoft Outlook accounts for linkgit:git-send-email[1])\n-\n CREDENTIAL CONTEXTS\n -------------------\n \n-- \n2.49.0\n\n"},{"id":"518444","messageId":"xmqqsel0mp8d.fsf@gitster.g","threadId":"63454","inReplyTo":"A84F634C-3423-48E2-B648-068A75423037@live.com","subject":"Re: [PATCH v4 0/3] docs: update email credential helpers and improve formatting","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-05-19T18:26:10Z","receivedAt":"2025-05-19T18:26:14Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Aditya Garg writes:\n\n> 2. The second patch improves the formatting of the `git-send-email`\n> documentation, making it more readable and consistent.\n\nWhat does this series build on? The patch apparently does not seem\nto apply to any recent tips of 'master'.\n\nWhen you are not building on 'master', please leave a note to say\nthings like:\n\n - Because this breakage was introduced between Git 2.43 and Git\n 2.44, and the area of the code hasn't changed since then, these\n patches are made against Git 2.44.0; the result applying this\n series there merges cleanly to 'master', too.\n\n - This change depends on the topic, xy/frotz, which hasn't been\n merged to 'master'. The patches are made on top of the result of\n merging that topic to 'master'.\n\nI am guessing that this is meant to apply on top of a merge of\nag/doc-send-email ba998f61 (docs: add credential helper for outlook\nand gmail in OAuth list of helpers, 2025-05-08) into 'master', so\nI'll tentatively queue them there.\n\nThanks.\n\n\n"},{"id":"518445","messageId":"PN3PR01MB9597D02747FD9F3091C03C27B89CA@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"xmqqsel0mp8d.fsf@gitster.g","subject":"Re: [PATCH v4 0/3] docs: update email credential helpers and improve formatting","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-19T18:29:57Z","receivedAt":"2025-05-19T18:30:05Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\nOn 19/05/25 11:56 pm, Junio C Hamano wrote:\n> Aditya Garg writes:\n> \n>> 2. The second patch improves the formatting of the `git-send-email`\n>> documentation, making it more readable and consistent.\n> \n> What does this series build on? The patch apparently does not seem\n> to apply to any recent tips of 'master'.\n> \n> When you are not building on 'master', please leave a note to say\n> things like:\n> \n> - Because this breakage was introduced between Git 2.43 and Git\n> 2.44, and the area of the code hasn't changed since then, these\n> patches are made against Git 2.44.0; the result applying this\n> series there merges cleanly to 'master', too.\n> \n> - This change depends on the topic, xy/frotz, which hasn't been\n> merged to 'master'. The patches are made on top of the result of\n> merging that topic to 'master'.\n\nI'm sorry, I'll make sure I specify that in the future.\n\n> \n> I am guessing that this is meant to apply on top of a merge of\n> ag/doc-send-email ba998f61 (docs: add credential helper for outlook\n> and gmail in OAuth list of helpers, 2025-05-08) into 'master', so\n> I'll tentatively queue them there.\n\nYes you are correct!\n"},{"id":"519050","messageId":"20250528070521.17379-1-gargaditya08@live.com","threadId":"63454","inReplyTo":"PN3PR01MB95971131BD3CD89771F19E5DB896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"[PATCH v5 0/4] docs: update email credential helpers and improve formatting","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-28T07:05:27Z","receivedAt":"2025-05-28T07:05:32Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"Hi all,\n\nThis patch series included three patches:\n\n1. The first patch adds a link to the `git-credential-yahoo` helper for\n Yahoo accounts and links Google's `sendgmail` tool as an alternative\n method for sending emails through Gmail.\n\n2. The second patch improves the formatting of the `git-send-email`\n documentation, making it more readable and consistent.\n\n3. The third patch removed the email credential helper links from the\n `gitcredentials` page. The links are still available in the\n `git-send-email` documentation, which is the right place for them.\n\nDetailed explanation of the changes has been done in individual patch.\n\nv2: Removed instructions for Yahoo SMTP server since I've realised that\n Yahoo *was* a popular email service. Also, the instructions were\n just making the docs more crowded. I've also added a link to\n Google's `sendgmail` tool in the first patch. The second patch has been\n added to address the issues that came up here:\n https://github.com/git/git-scm.com/pull/2005\n\nv3: Added a patch to improve the formatting of the `git-send-email`\n documentation.\n\nv4: Added cpan links of the perl modules requires for `git-send-email`\n to work.\n\nv5: Added a patch to make the purpose of using app password for Gmail\n more clear in `send-email` documentation.\n\nAditya Garg (4):\n docs: add credential helper for yahoo and link Google's sendgmail tool\n docs: improve formatting in git-send-email documentation\n docs: remove credential helper links for emails from gitcredentials\n docs: make the purpose of using app password for Gmail more clear in\n send-email\n\n Documentation/config/sendemail.adoc | 8 +-\n Documentation/git-send-email.adoc | 194 +++++++++++++++-------------\n Documentation/gitcredentials.adoc | 4 -\n 3 files changed, 109 insertions(+), 97 deletions(-)\n\nRange-diff:\n-: ---------- > 1: 2c47cc5396 docs: add credential helper for yahoo and link Google's sendgmail tool\n-: ---------- > 2: bc1d0471ca docs: improve formatting in git-send-email documentation\n-: ---------- > 3: b9e41e2492 docs: remove credential helper links for emails from gitcredentials\n-: ---------- > 4: a6ad7ac810 docs: make the purpose of using app password for Gmail more clear in send-email\n-- \n2.43.0\n\n"},{"id":"519051","messageId":"20250528070521.17379-2-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250528070521.17379-1-gargaditya08@live.com","subject":"[PATCH v5 1/4] docs: add credential helper for yahoo and link Google's sendgmail tool","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-28T07:05:32Z","receivedAt":"2025-05-28T07:05:35Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"This commit links `git-credential-yahoo` as a credential helper for\nYahoo accounts. Also, Google's `sendgmail` tool has been linked as an\nalternative method for sending emails through Gmail.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/git-send-email.adoc | 10 ++++++++--\n 1 file changed, 8 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 26fda63c2f..81f8cbc6f3 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -543,6 +543,10 @@ settings:\n \tsmtpAuth = OAUTHBEARER\n ----\n \n+Alternatively, you can use a tool developed by Google known as\n+https://github.com/google/gmail-oauth2-tools/tree/master/go/sendgmail[sendgmail]\n+to send emails using `git send-email`.\n+\n Use Microsoft Outlook as the SMTP Server\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.\n@@ -579,8 +583,7 @@ next time.\n \n If you are using OAuth2.0 authentication, you need to use an access token in\n place of a password when prompted. Various OAuth2.0 token generators are\n-available online. Community maintained credential helpers for Gmail and Outlook\n-are also available:\n+available online. Community maintained credential helpers are also available:\n \n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail]\n \t (cross platform, dedicated helper for authenticating Gmail accounts)\n@@ -588,6 +591,9 @@ are also available:\n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook]\n \t (cross platform, dedicated helper for authenticating Microsoft Outlook accounts)\n \n+\t- https://github.com/AdityaGarg8/git-credential-email[git-credential-yahoo]\n+\t (cross platform, dedicated helper for authenticating Yahoo accounts)\n+\n You can also see linkgit:gitcredentials[7] for more OAuth based authentication\n helpers.\n \n-- \n2.43.0\n\n"},{"id":"519052","messageId":"20250528070521.17379-3-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250528070521.17379-1-gargaditya08@live.com","subject":"[PATCH v5 2/4] docs: improve formatting in git-send-email documentation","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-28T07:05:34Z","receivedAt":"2025-05-28T07:05:39Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"The current documentation for git-send-email had an inconsistent use of\n\"\", ``, and '' for quoting. This commit improves the formatting by\nusing the same style throughout the documentation.\n\nAlso, at some places, minor grammatical errors were fixed, and some\nnon existent links were removed.\n\nFinally, the cpan links of necessary perl modules have been added to\nmake their installation easier.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/config/sendemail.adoc | 8 +-\n Documentation/git-send-email.adoc | 181 +++++++++++++++-------------\n 2 files changed, 98 insertions(+), 91 deletions(-)\n\ndiff --git a/Documentation/config/sendemail.adoc b/Documentation/config/sendemail.adoc\nindex 5ffcfc9f2a..0b1b2766f5 100644\n--- a/Documentation/config/sendemail.adoc\n+++ b/Documentation/config/sendemail.adoc\n@@ -19,9 +19,9 @@ sendemail..*::\n \t`sendemail.identity`.\n \n sendemail.multiEdit::\n-\tIf true (default), a single editor instance will be spawned to edit\n+\tIf `true` (default), a single editor instance will be spawned to edit\n \tfiles you have to edit (patches when `--annotate` is used, and the\n-\tsummary when `--compose` is used). If false, files will be edited one\n+\tsummary when `--compose` is used). If `false`, files will be edited one\n \tafter the other, spawning a new editor each time.\n \n sendemail.confirm::\n@@ -101,7 +101,7 @@ sendemail.signedOffCc (deprecated)::\n \n sendemail.smtpBatchSize::\n \tNumber of messages to be sent per connection, after that a relogin\n-\twill happen. If the value is 0 or undefined, send all messages in\n+\twill happen. If the value is `0` or undefined, send all messages in\n \tone connection.\n \tSee also the `--batch-size` option of linkgit:git-send-email[1].\n \n@@ -111,5 +111,5 @@ sendemail.smtpReloginDelay::\n \n sendemail.forbidSendmailVariables::\n \tTo avoid common misconfiguration mistakes, linkgit:git-send-email[1]\n-\twill abort with a warning if any configuration options for \"sendmail\"\n+\twill abort with a warning if any configuration options for `sendmail`\n \texist. Set this variable to bypass the check.\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 81f8cbc6f3..aff0861d29 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -21,7 +21,7 @@ Takes the patches given on the command line and emails them out.\n Patches can be specified as files, directories (which will send all\n files in the directory), or directly as a revision list. In the\n last case, any format accepted by linkgit:git-format-patch[1] can\n-be passed to git send-email, as well as options understood by\n+be passed to `git send-email`, as well as options understood by\n linkgit:git-format-patch[1].\n \n The header of the email is configurable via command-line options. If not\n@@ -35,11 +35,11 @@ There are two formats accepted for patch files:\n This is what linkgit:git-format-patch[1] generates. Most headers and MIME\n formatting are ignored.\n \n-2. The original format used by Greg Kroah-Hartman's 'send_lots_of_email.pl'\n+2. The original format used by Greg Kroah-Hartman's `send_lots_of_email.pl`\n script\n +\n-This format expects the first line of the file to contain the \"Cc:\" value\n-and the \"Subject:\" of the message as the second line.\n+This format expects the first line of the file to contain the 'Cc:' value\n+and the 'Subject:' of the message as the second line.\n \n \n OPTIONS\n@@ -54,13 +54,13 @@ Composing\n \t`sendemail.multiEdit`.\n \n --bcc=
,...::\n-\tSpecify a \"Bcc:\" value for each email. Default is the value of\n+\tSpecify a 'Bcc:' value for each email. Default is the value of\n \t`sendemail.bcc`.\n +\n This option may be specified multiple times.\n \n --cc=
,...::\n-\tSpecify a starting \"Cc:\" value for each email.\n+\tSpecify a starting 'Cc:' value for each email.\n \tDefault is the value of `sendemail.cc`.\n +\n This option may be specified multiple times.\n@@ -69,14 +69,14 @@ This option may be specified multiple times.\n \tInvoke a text editor (see GIT_EDITOR in linkgit:git-var[1])\n \tto edit an introductory message for the patch series.\n +\n-When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n-Subject, Reply-To, and In-Reply-To headers specified in the message. If\n-the body of the message (what you type after the headers and a blank\n-line) only contains blank (or Git: prefixed) lines, the summary won't be\n+When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n+'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n+message. If the body of the message (what you type after the headers and a\n+blank line) only contains blank (or Git: prefixed) lines, the summary won't be\n sent, but the headers mentioned above will be used unless they are\n removed.\n +\n-Missing From or In-Reply-To headers will be prompted for.\n+Missing 'From' or 'In-Reply-To' headers will be prompted for.\n +\n See the CONFIGURATION section for `sendemail.multiEdit`.\n \n@@ -85,13 +85,13 @@ See the CONFIGURATION section for `sendemail.multiEdit`.\n \tthe value of the `sendemail.from` configuration option is used. If\n \tneither the command-line option nor `sendemail.from` are set, then the\n \tuser will be prompted for the value. The default for the prompt will be\n-\tthe value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not\n-\tset, as returned by \"git var -l\".\n+\tthe value of `GIT_AUTHOR_IDENT`, or `GIT_COMMITTER_IDENT` if that is not\n+\tset, as returned by `git var -l`.\n \n --reply-to=
::\n \tSpecify the address where replies from recipients should go to.\n \tUse this if replies to messages should go to another address than what\n-\tis specified with the --from parameter.\n+\tis specified with the `--from` parameter.\n \n --in-reply-to=::\n \tMake the first mail (or all the mails with `--no-thread`) appear as a\n@@ -112,14 +112,14 @@ illustration below where `[PATCH v2 0/3]` is in reply to `[PATCH 0/2]`:\n [PATCH v2 2/3] New tests\n [PATCH v2 3/3] Implementation\n +\n-Only necessary if --compose is also set. If --compose\n+Only necessary if `--compose` is also set. If `--compose`\n is not set, this will be prompted for.\n \n --[no-]outlook-id-fix::\n \tMicrosoft Outlook SMTP servers discard the Message-ID sent via email and\n \tassign a new random Message-ID, thus breaking threads.\n +\n-With `--outlook-id-fix`, 'git send-email' uses a mechanism specific to\n+With `--outlook-id-fix`, `git send-email` uses a mechanism specific to\n Outlook servers to learn the Message-ID the server assigned to fix the\n threading. Use it only when you know that the server reports the\n rewritten Message-ID the same way as Outlook servers do.\n@@ -130,14 +130,14 @@ to 'smtp.office365.com' or 'smtp-mail.outlook.com'. Use\n \n --subject=::\n \tSpecify the initial subject of the email thread.\n-\tOnly necessary if --compose is also set. If --compose\n+\tOnly necessary if `--compose` is also set. If `--compose`\n \tis not set, this will be prompted for.\n \n --to=
,...::\n \tSpecify the primary recipient of the emails generated. Generally, this\n \twill be the upstream maintainer of the project involved. Default is the\n \tvalue of the `sendemail.to` configuration value; if that is unspecified,\n-\tand --to-cmd is not specified, this will be prompted for.\n+\tand `--to-cmd` is not specified, this will be prompted for.\n +\n This option may be specified multiple times.\n \n@@ -145,30 +145,30 @@ This option may be specified multiple times.\n \tWhen encountering a non-ASCII message or subject that does not\n \tdeclare its encoding, add headers/quoting to indicate it is\n \tencoded in . Default is the value of the\n-\t'sendemail.assume8bitEncoding'; if that is unspecified, this\n+\t`sendemail.assume8bitEncoding`; if that is unspecified, this\n \twill be prompted for if any non-ASCII files are encountered.\n +\n Note that no attempts whatsoever are made to validate the encoding.\n \n --compose-encoding=::\n \tSpecify encoding of compose message. Default is the value of the\n-\t'sendemail.composeEncoding'; if that is unspecified, UTF-8 is assumed.\n+\t`sendemail.composeEncoding`; if that is unspecified, UTF-8 is assumed.\n \n --transfer-encoding=(7bit|8bit|quoted-printable|base64|auto)::\n \tSpecify the transfer encoding to be used to send the message over SMTP.\n-\t7bit will fail upon encountering a non-ASCII message. quoted-printable\n+\t'7bit' will fail upon encountering a non-ASCII message. 'quoted-printable'\n \tcan be useful when the repository contains files that contain carriage\n-\treturns, but makes the raw patch email file (as saved from a MUA) much\n-\tharder to inspect manually. base64 is even more fool proof, but also\n-\teven more opaque. auto will use 8bit when possible, and quoted-printable\n-\totherwise.\n+\treturns, but makes the raw patch email file (as saved from an MUA) much\n+\tharder to inspect manually. 'base64' is even more fool proof, but also\n+\teven more opaque. 'auto' will use '8bit' when possible, and\n+\t'quoted-printable' otherwise.\n +\n Default is the value of the `sendemail.transferEncoding` configuration\n-value; if that is unspecified, default to `auto`.\n+value; if that is unspecified, default to 'auto'.\n \n --xmailer::\n --no-xmailer::\n-\tAdd (or prevent adding) the \"X-Mailer:\" header. By default,\n+\tAdd (or prevent adding) the 'X-Mailer:' header. By default,\n \tthe header is added, but it can be turned off by setting the\n \t`sendemail.xmailer` configuration variable to `false`.\n \n@@ -179,8 +179,8 @@ Sending\n \tSpecify the envelope sender used to send the emails.\n \tThis is useful if your default address is not the address that is\n \tsubscribed to a list. In order to use the 'From' address, set the\n-\tvalue to \"auto\". If you use the sendmail binary, you must have\n-\tsuitable privileges for the -f parameter. Default is the value of the\n+\tvalue to `auto`. If you use the `sendmail` binary, you must have\n+\tsuitable privileges for the `-f` parameter. Default is the value of the\n \t`sendemail.envelopeSender` configuration variable; if that is\n \tunspecified, choosing the envelope sender is left to your MTA.\n \n@@ -189,8 +189,8 @@ Sending\n \tbe sendmail-like; specifically, it must support the `-i` option.\n \tThe command will be executed in the shell if necessary. Default\n \tis the value of `sendemail.sendmailCmd`. If unspecified, and if\n-\t--smtp-server is also unspecified, git-send-email will search\n-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH.\n+\t`--smtp-server` is also unspecified, `git send-email` will search\n+\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH`.\n \n --smtp-encryption=::\n \tSpecify in what way encrypting begins for the SMTP connection.\n@@ -209,7 +209,7 @@ Sending\n --smtp-domain=::\n \tSpecifies the Fully Qualified Domain Name (FQDN) used in the\n \tHELO/EHLO command to the SMTP server. Some servers require the\n-\tFQDN to match your IP address. If not set, git send-email attempts\n+\tFQDN to match your IP address. If not set, `git send-email` attempts\n \tto determine your FQDN automatically. Default is the value of\n \t`sendemail.smtpDomain`.\n \n@@ -223,10 +223,10 @@ $ git send-email --smtp-auth=\"PLAIN LOGIN GSSAPI\" ...\n +\n If at least one of the specified mechanisms matches the ones advertised by the\n SMTP server and if it is supported by the utilized SASL library, the mechanism\n-is used for authentication. If neither 'sendemail.smtpAuth' nor `--smtp-auth`\n+is used for authentication. If neither `sendemail.smtpAuth` nor `--smtp-auth`\n is specified, all mechanisms supported by the SASL library can be used. The\n-special value 'none' maybe specified to completely disable authentication\n-independently of `--smtp-user`\n+special value `none` maybe specified to completely disable authentication\n+independently of `--smtp-user`.\n \n --smtp-pass[=]::\n \tPassword for SMTP-AUTH. The argument is optional: If no\n@@ -238,16 +238,16 @@ Furthermore, passwords need not be specified in configuration files\n or on the command line. If a username has been specified (with\n `--smtp-user` or a `sendemail.smtpUser`), but no password has been\n specified (with `--smtp-pass` or `sendemail.smtpPass`), then\n-a password is obtained using 'git-credential'.\n+a password is obtained using linkgit:git-credential[1].\n \n --no-smtp-auth::\n-\tDisable SMTP authentication. Short hand for `--smtp-auth=none`\n+\tDisable SMTP authentication. Short hand for `--smtp-auth=none`.\n \n --smtp-server=::\n \tIf set, specifies the outgoing SMTP server to use (e.g.\n \t`smtp.example.com` or a raw IP address). If unspecified, and if\n \t`--sendmail-cmd` is also unspecified, the default is to search\n-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH if such a\n+\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH` if such a\n \tprogram is available, falling back to `localhost` otherwise.\n +\n For backward compatibility, this option can also specify a full pathname\n@@ -260,7 +260,7 @@ instead.\n \tSpecifies a port different from the default port (SMTP\n \tservers typically listen to smtp port 25, but may also listen to\n \tsubmission port 587, or the common SSL smtp port 465);\n-\tsymbolic port names (e.g. \"submission\" instead of 587)\n+\tsymbolic port names (e.g. `submission` instead of 587)\n \tare also accepted. The port can also be set with the\n \t`sendemail.smtpServerPort` configuration variable.\n \n@@ -269,7 +269,7 @@ instead.\n \tDefault value can be specified by the `sendemail.smtpServerOption`\n \tconfiguration option.\n +\n-The --smtp-server-option option must be repeated for each option you want\n+The `--smtp-server-option` option must be repeated for each option you want\n to pass to the server. Likewise, different lines in the configuration files\n must be used for each option.\n \n@@ -279,9 +279,8 @@ must be used for each option.\n --smtp-ssl-cert-path::\n \tPath to a store of trusted CA certificates for SMTP SSL/TLS\n \tcertificate validation (either a directory that has been processed\n-\tby 'c_rehash', or a single file containing one or more PEM format\n-\tcertificates concatenated together: see verify(1) -CAfile and\n-\t-CApath for more information on these). Set it to an empty string\n+\tby `c_rehash`, or a single file containing one or more PEM format\n+\tcertificates concatenated together). Set it to an empty string\n \tto disable certificate verification. Defaults to the value of the\n \t`sendemail.smtpSSLCertPath` configuration variable, if set, or the\n \tbacking SSL library's compiled-in default otherwise (which should\n@@ -298,18 +297,18 @@ must be used for each option.\n \tconnection and authentication problems.\n \n --batch-size=::\n-\tSome email servers (e.g. smtp.163.com) limit the number emails to be\n+\tSome email servers (e.g. 'smtp.163.com') limit the number of emails to be\n \tsent per session (connection) and this will lead to a failure when\n \tsending many messages. With this option, send-email will disconnect after\n-\tsending $ messages and wait for a few seconds (see --relogin-delay)\n-\tand reconnect, to work around such a limit. You may want to\n-\tuse some form of credential helper to avoid having to retype\n-\tyour password every time this happens. Defaults to the\n+\tsending `$` messages and wait for a few seconds\n+\t(see `--relogin-delay`) and reconnect, to work around such a limit.\n+\tYou may want to use some form of credential helper to avoid having to\n+\tretype your password every time this happens. Defaults to the\n \t`sendemail.smtpBatchSize` configuration variable.\n \n --relogin-delay=::\n-\tWaiting $ seconds before reconnecting to SMTP server. Used together\n-\twith --batch-size option. Defaults to the `sendemail.smtpReloginDelay`\n+\tWaiting `$` seconds before reconnecting to SMTP server. Used together\n+\twith `--batch-size` option. Defaults to the `sendemail.smtpReloginDelay`\n \tconfiguration variable.\n \n Automating\n@@ -318,7 +317,7 @@ Automating\n --no-to::\n --no-cc::\n --no-bcc::\n-\tClears any list of \"To:\", \"Cc:\", \"Bcc:\" addresses previously\n+\tClears any list of 'To:', 'Cc:', 'Bcc:' addresses previously\n \tset via config.\n \n --no-identity::\n@@ -327,13 +326,13 @@ Automating\n \n --to-cmd=::\n \tSpecify a command to execute once per patch file which\n-\tshould generate patch file specific \"To:\" entries.\n+\tshould generate patch file specific 'To:' entries.\n \tOutput of this command must be single email address per line.\n-\tDefault is the value of 'sendemail.toCmd' configuration value.\n+\tDefault is the value of `sendemail.toCmd` configuration value.\n \n --cc-cmd=::\n \tSpecify a command to execute once per patch file which\n-\tshould generate patch file specific \"Cc:\" entries.\n+\tshould generate patch file specific 'Cc:' entries.\n \tOutput of this command must be single email address per line.\n \tDefault is the value of `sendemail.ccCmd` configuration value.\n \n@@ -341,7 +340,7 @@ Automating\n \tSpecify a command that is executed once per outgoing message\n \tand output RFC 2822 style header lines to be inserted into\n \tthem. When the `sendemail.headerCmd` configuration variable is\n-\tset, its value is always used. When --header-cmd is provided\n+\tset, its value is always used. When `--header-cmd` is provided\n \tat the command line, its value takes precedence over the\n \t`sendemail.headerCmd` configuration variable.\n \n@@ -350,7 +349,7 @@ Automating\n \n --[no-]chain-reply-to::\n \tIf this is set, each email will be sent as a reply to the previous\n-\temail sent. If disabled with \"--no-chain-reply-to\", all emails after\n+\temail sent. If disabled with `--no-chain-reply-to`, all emails after\n \tthe first will be sent as replies to the first email sent. When using\n \tthis, it is recommended that the first file given be an overview of the\n \tentire patch series. Disabled by default, but the `sendemail.chainReplyTo`\n@@ -363,21 +362,22 @@ Automating\n \tthe value of `sendemail.identity`.\n \n --[no-]signed-off-by-cc::\n-\tIf this is set, add emails found in the `Signed-off-by` trailer or Cc: lines to the\n-\tcc list. Default is the value of `sendemail.signedOffByCc` configuration\n-\tvalue; if that is unspecified, default to --signed-off-by-cc.\n+\tIf this is set, add emails found in the `Signed-off-by` trailer or 'Cc:'\n+\tlines to the cc list. Default is the value of `sendemail.signedOffByCc`\n+\tconfiguration value; if that is unspecified, default to\n+\t`--signed-off-by-cc`.\n \n --[no-]cc-cover::\n-\tIf this is set, emails found in Cc: headers in the first patch of\n+\tIf this is set, emails found in 'Cc:' headers in the first patch of\n \tthe series (typically the cover letter) are added to the cc list\n-\tfor each email set. Default is the value of 'sendemail.ccCover'\n-\tconfiguration value; if that is unspecified, default to --no-cc-cover.\n+\tfor each email set. Default is the value of `sendemail.ccCover`\n+\tconfiguration value; if that is unspecified, default to `--no-cc-cover`.\n \n --[no-]to-cover::\n-\tIf this is set, emails found in To: headers in the first patch of\n+\tIf this is set, emails found in 'To:' headers in the first patch of\n \tthe series (typically the cover letter) are added to the to list\n-\tfor each email set. Default is the value of 'sendemail.toCover'\n-\tconfiguration value; if that is unspecified, default to --no-to-cover.\n+\tfor each email set. Default is the value of `sendemail.toCover`\n+\tconfiguration value; if that is unspecified, default to `--no-to-cover`.\n \n --suppress-cc=::\n \tSpecify an additional category of recipients to suppress the\n@@ -401,36 +401,36 @@ Automating\n --\n +\n Default is the value of `sendemail.suppressCc` configuration value; if\n-that is unspecified, default to 'self' if --suppress-from is\n-specified, as well as 'body' if --no-signed-off-cc is specified.\n+that is unspecified, default to 'self' if `--suppress-from` is\n+specified, as well as 'body' if `--no-signed-off-cc` is specified.\n \n --[no-]suppress-from::\n-\tIf this is set, do not add the From: address to the cc: list.\n+\tIf this is set, do not add the 'From:' address to the 'Cc:' list.\n \tDefault is the value of `sendemail.suppressFrom` configuration\n-\tvalue; if that is unspecified, default to --no-suppress-from.\n+\tvalue; if that is unspecified, default to `--no-suppress-from`.\n \n --[no-]thread::\n-\tIf this is set, the In-Reply-To and References headers will be\n+\tIf this is set, the 'In-Reply-To' and 'References' headers will be\n \tadded to each email sent. Whether each mail refers to the\n-\tprevious email (`deep` threading per 'git format-patch'\n+\tprevious email (`deep` threading per `git format-patch`\n \twording) or to the first email (`shallow` threading) is\n-\tgoverned by \"--[no-]chain-reply-to\".\n+\tgoverned by `--[no-]chain-reply-to`.\n +\n-If disabled with \"--no-thread\", those headers will not be added\n-(unless specified with --in-reply-to). Default is the value of the\n+If disabled with `--no-thread`, those headers will not be added\n+(unless specified with `--in-reply-to`). Default is the value of the\n `sendemail.thread` configuration value; if that is unspecified,\n-default to --thread.\n+default to `--thread`.\n +\n It is up to the user to ensure that no In-Reply-To header already\n-exists when 'git send-email' is asked to add it (especially note that\n-'git format-patch' can be configured to do the threading itself).\n+exists when `git send-email` is asked to add it (especially note that\n+`git format-patch` can be configured to do the threading itself).\n Failure to do so may not produce the expected result in the\n recipient's MUA.\n \n --[no-]mailmap::\n \tUse the mailmap file (see linkgit:gitmailmap[5]) to map all\n \taddresses to their canonical real name and email address. Additional\n-\tmailmap data specific to git-send-email may be provided using the\n+\tmailmap data specific to `git send-email` may be provided using the\n \t`sendemail.mailmap.file` or `sendemail.mailmap.blob` configuration\n \tvalues. Defaults to `sendemail.mailmap`.\n \n@@ -441,12 +441,12 @@ Administering\n \tConfirm just before sending:\n +\n --\n-- 'always' will always confirm before sending\n-- 'never' will never confirm before sending\n+- 'always' will always confirm before sending.\n+- 'never' will never confirm before sending.\n - 'cc' will confirm before sending when send-email has automatically\n- added addresses from the patch to the Cc list\n+ added addresses from the patch to the Cc list.\n - 'compose' will confirm before sending the first message when using --compose.\n-- 'auto' is equivalent to 'cc' + 'compose'\n+- 'auto' is equivalent to 'cc' + 'compose'.\n --\n +\n Default is the value of `sendemail.confirm` configuration value; if that\n@@ -460,10 +460,10 @@ have been specified, in which case default to 'compose'.\n \tWhen an argument may be understood either as a reference or as a file name,\n \tchoose to understand it as a format-patch argument (`--format-patch`)\n \tor as a file name (`--no-format-patch`). By default, when such a conflict\n-\toccurs, git send-email will fail.\n+\toccurs, `git send-email` will fail.\n \n --quiet::\n-\tMake git-send-email less verbose. One line per email should be\n+\tMake `git send-email` less verbose. One line per email should be\n \tall that is output.\n \n --[no-]validate::\n@@ -525,7 +525,7 @@ edit `~/.gitconfig` to specify your account settings:\n ----\n \n If you have multi-factor authentication set up on your Gmail account, you can\n-generate an app-specific password for use with 'git send-email'. Visit\n+generate an app-specific password for use with `git send-email`. Visit\n https://security.google.com/settings/security/apppasswords to create it.\n \n You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n@@ -599,9 +599,16 @@ helpers.\n \n Note: the following core Perl modules that may be installed with your\n distribution of Perl are required:\n-MIME::Base64, MIME::QuotedPrint, Net::Domain and Net::SMTP.\n+\n+https://metacpan.org/pod/MIME::Base64[MIME::Base64],\n+https://metacpan.org/pod/MIME::QuotedPrint[MIME::QuotedPrint],\n+https://metacpan.org/pod/Net::Domain[Net::Domain] and\n+https://metacpan.org/pod/Net::SMTP[Net::SMTP].\n+\n These additional Perl modules are also required:\n-Authen::SASL and Mail::Address.\n+\n+https://metacpan.org/pod/Authen::SASL[Authen::SASL] and\n+https://metacpan.org/pod/Mail::Address[Mail::Address].\n \n \n SEE ALSO\n-- \n2.43.0\n\n"},{"id":"519053","messageId":"20250528070521.17379-5-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250528070521.17379-1-gargaditya08@live.com","subject":"[PATCH v5 4/4] docs: make the purpose of using app password for Gmail more clear in send-email","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-28T07:05:38Z","receivedAt":"2025-05-28T07:05:44Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"The current example for Gmail suggests using app passwords for\nsend-email if user has multi-factor authentication set up for their\naccount. However, it does not clarify that the user cannot use their\nnormal password in case they do not have multi-factor authentication\nenabled. Most likely the example was written in the days when Google\nallowed using normal passwords without multi-factor authentication.\n\nThis commit clarifies that app passwords are required and suggests using\nOAuth2 if the user does not want to enable multi-factor authentication.\n---\n Documentation/git-send-email.adoc | 3 +++\n 1 file changed, 3 insertions(+)\n\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex aff0861d29..99c126cd5a 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -524,9 +524,12 @@ edit `~/.gitconfig` to specify your account settings:\n \tsmtpServerPort = 587\n ----\n \n+Gmail does not allow using your account password for `git send-email`.\n If you have multi-factor authentication set up on your Gmail account, you can\n generate an app-specific password for use with `git send-email`. Visit\n https://security.google.com/settings/security/apppasswords to create it.\n+If you do not want to enable multi-factor authentication, you can use OAuth2.0\n+authentication as described below.\n \n You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n `XOAUTH2` are common methods used for this type of authentication. Gmail\n-- \n2.43.0\n\n"},{"id":"519054","messageId":"20250528070521.17379-4-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250528070521.17379-1-gargaditya08@live.com","subject":"[PATCH v5 3/4] docs: remove credential helper links for emails from gitcredentials","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-28T07:05:36Z","receivedAt":"2025-05-28T07:05:48Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"In a recent attempt to add links of email helpers to git-scm.com [1], I\ncame to a conclusion that the links in the gitcredentials page are meant\nfor people needing credential helpers for cloning, fetching and pushing\nrepositories to remote hosts, and not sending emails. gitcredentials\ndocs don't even talk about send emails, thus confirming this view.\n\nSo, lets remove these links from the gitcredentials page. The links are\nstill available in the git-send-email documentation, which is the right\nplace for them.\n\n[1]: https://github.com/git/git-scm.com/pull/2005\n\nSigned-off-by: Aditya Garg \n---\n Documentation/gitcredentials.adoc | 4 ----\n 1 file changed, 4 deletions(-)\n\ndiff --git a/Documentation/gitcredentials.adoc b/Documentation/gitcredentials.adoc\nindex b49923db02..3337bb475d 100644\n--- a/Documentation/gitcredentials.adoc\n+++ b/Documentation/gitcredentials.adoc\n@@ -133,10 +133,6 @@ Popular helpers with OAuth support include:\n \n - https://github.com/hickford/git-credential-oauth[git-credential-oauth] (cross platform, included in many Linux distributions)\n \n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail] (cross platform, dedicated helper to authenticate Gmail accounts for linkgit:git-send-email[1])\n-\n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook] (cross platform, dedicated helper to authenticate Microsoft Outlook accounts for linkgit:git-send-email[1])\n-\n CREDENTIAL CONTEXTS\n -------------------\n \n-- \n2.43.0\n\n"},{"id":"519058","messageId":"CAPig+cTs0+AUPp1euxqKkX0iFTdw9zGuMU-Qnp+ywhcyP8gxfA@mail.gmail.com","threadId":"63454","inReplyTo":"20250528070521.17379-1-gargaditya08@live.com","subject":"Re: [PATCH v5 0/4] docs: update email credential helpers and improve formatting","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2025-05-28T07:23:18Z","receivedAt":"2025-05-28T07:23:30Z","isPatch":true,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Wed, May 28, 2025 at 3:05 AM Aditya Garg wrote:\n> v5: Added a patch to make the purpose of using app password for Gmail\n> more clear in `send-email` documentation.\n>\n> Range-diff:\n> -: ---------- > 1: 2c47cc5396 docs: add credential helper for yahoo and link Google's sendgmail tool\n> -: ---------- > 2: bc1d0471ca docs: improve formatting in git-send-email documentation\n> -: ---------- > 3: b9e41e2492 docs: remove credential helper links for emails from gitcredentials\n> -: ---------- > 4: a6ad7ac810 docs: make the purpose of using app password for Gmail more clear in send-email\n\nStrange range-diff.\n"},{"id":"519067","messageId":"PN3PR01MB9597EBE360893FA638B17952B867A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"CAPig+cTs0+AUPp1euxqKkX0iFTdw9zGuMU-Qnp+ywhcyP8gxfA@mail.gmail.com","subject":"Re: [PATCH v5 0/4] docs: update email credential helpers and improve formatting","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-28T09:36:47Z","receivedAt":"2025-05-28T09:36:55Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\nOn 28-05-2025 12:53 pm, Eric Sunshine wrote:\n> On Wed, May 28, 2025 at 3:05 AM Aditya Garg wrote:\n>> v5: Added a patch to make the purpose of using app password for Gmail\n>> more clear in `send-email` documentation.\n>>\n>> Range-diff:\n>> -: ---------- > 1: 2c47cc5396 docs: add credential helper for yahoo and link Google's sendgmail tool\n>> -: ---------- > 2: bc1d0471ca docs: improve formatting in git-send-email documentation\n>> -: ---------- > 3: b9e41e2492 docs: remove credential helper links for emails from gitcredentials\n>> -: ---------- > 4: a6ad7ac810 docs: make the purpose of using app password for Gmail more clear in send-email\n> \n> Strange range-diff.\n\nI think because I used git version 2.43. When I compiled my branch with changes, git format-patch over there\nhad a very different range-diff from this.\n"},{"id":"519068","messageId":"PN3PR01MB95972C400AE59DAB2EB388A5B867A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"PN3PR01MB9597EBE360893FA638B17952B867A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"Re: [PATCH v5 0/4] docs: update email credential helpers and improve formatting","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-28T09:42:16Z","receivedAt":"2025-05-28T09:42:25Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\nOn 28-05-2025 03:06 pm, Aditya Garg wrote:\n> \n> \n> On 28-05-2025 12:53 pm, Eric Sunshine wrote:\n>> On Wed, May 28, 2025 at 3:05 AM Aditya Garg wrote:\n>>> v5: Added a patch to make the purpose of using app password for Gmail\n>>> more clear in `send-email` documentation.\n>>>\n>>> Range-diff:\n>>> -: ---------- > 1: 2c47cc5396 docs: add credential helper for yahoo and link Google's sendgmail tool\n>>> -: ---------- > 2: bc1d0471ca docs: improve formatting in git-send-email documentation\n>>> -: ---------- > 3: b9e41e2492 docs: remove credential helper links for emails from gitcredentials\n>>> -: ---------- > 4: a6ad7ac810 docs: make the purpose of using app password for Gmail more clear in send-email\n>>\n>> Strange range-diff.\n> \n> I think because I used git version 2.43. When I compiled my branch with changes, git format-patch over there\n> had a very different range-diff from this.\n\nI get this range-diff with git 2.49\n\nRange-diff:\n-: ---------- > 1: 4757d0305d imap-send: fix bug causing cfg->folder being set to NULL\n1: 62edbcfc6e ! 2: f5ad01abc5 imap-send: enable specifying the folder using the command line\n @@ Metadata\n Author: Aditya Garg \n \n ## Commit message ##\n - imap-send: enable specifying the folder using the command line\n + imap-send: add support for OAuth2.0 authentication\n \n - Some users may very often want to imap-send messages to a folder\n - other than the default set in the config. Add a command line\n - argument for the same.\n + OAuth2.0 is a new way of authentication supported by various email providers\n + these days. OAUTHBEARER and XOAUTH2 are the two most common mechanisms used\n + for OAuth2.0. OAUTHBEARER is described in RFC5801[1] and RFC7628[2], whereas\n + XOAUTH2 is Google's proprietary mechanism (See [3]).\n +\n + [1]: https://datatracker.ietf.org/doc/html/rfc5801\n + [2]: https://datatracker.ietf.org/doc/html/rfc7628\n + [3]: https://developers.google.com/workspace/gmail/imap/xoauth2-protocol#initial_client_response\n \n Signed-off-by: Aditya Garg \n \n ## Documentation/config/imap.adoc ##\n -@@\n - imap.folder::\n - \tThe folder to drop the mails into, which is typically the Drafts\n --\tfolder. For example: \"INBOX.Drafts\", \"INBOX/Drafts\" or\n --\t\"[Gmail]/Drafts\". Required.\n -+\tfolder. For example: 'INBOX.Drafts', 'INBOX/Drafts' or\n -+\t'[Gmail]/Drafts'. Required if `--folder` argument is not used. If\n -+\tset and `--folder` is also used, `--folder` will be preferred.\n - \n - imap.tunnel::\n - \tCommand used to set up a tunnel to the IMAP server through which\n +@@ Documentation/config/imap.adoc: imap.authMethod::\n + \tSpecify the authentication method for authenticating with the IMAP server.\n + \tIf Git was built with the NO_CURL option, or if your curl version is older\n + \tthan 7.34.0, or if you're running git-imap-send with the `--no-curl`\n +-\toption, the only supported method is 'CRAM-MD5'. If this is not set\n +-\tthen 'git imap-send' uses the basic IMAP plaintext LOGIN command.\n ++\toption, the only supported methods are 'CRAM-MD5', 'OAUTHBEARER' and\n ++\t'XOAUTH2'. If this is not set then `git imap-send` uses the basic IMAP\n ++\tplaintext LOGIN command.\n \n ## Documentation/git-imap-send.adoc ##\n -@@ Documentation/git-imap-send.adoc: OPTIONS\n - --quiet::\n - \tBe quiet.\n - \n -+-f ::\n -+--folder ::\n -+\tSpecify the folder in which the emails have to saved.\n -+\tFor example: `--folder [Gmail]/Drafts` or `-f INBOX/Drafts`.\n -+\n - --curl::\n - \tUse libcurl to communicate with the IMAP server, unless tunneling\n - \tinto it. Ignored if Git was built without the USE_CURL_FOR_IMAP_SEND\n +@@ Documentation/git-imap-send.adoc: Using Gmail's IMAP interface:\n + \n + ---------\n + [imap]\n +-\tfolder = \"[Gmail]/Drafts\"\n +-\thost = imaps://imap.gmail.com\n +-\tuser = user@gmail.com\n +-\tport = 993\n ++ folder = \"[Gmail]/Drafts\"\n ++ host = imaps://imap.gmail.com\n ++ user = user@gmail.com\n ++ port = 993\n + ---------\n + \n ++Gmail does not allow using your account password for `git imap-send`.\n ++If you have multi-factor authentication set up on your Gmail account, you can generate\n ++an app-specific password for use with `git imap-send`.\n ++Visit https://security.google.com/settings/security/apppasswords to create it.\n ++If you do not want to enable multi-factor authentication, you can use OAuth2.0\n ++authentication as described below.\n ++\n + [NOTE]\n + You might need to instead use: `folder = \"[Google Mail]/Drafts\"` if you get an error\n + that the \"Folder doesn't exist\".\n +@@ Documentation/git-imap-send.adoc: that the \"Folder doesn't exist\".\n + If your Gmail account is set to another language than English, the name of the \"Drafts\"\n + folder will be localized.\n + \n ++If you want to use OAuth2.0 based authentication, you can specify `OAUTHBEARER`\n ++or `XOAUTH2` mechanism in your config. In such a case you will have to use an\n ++OAuth2.0 access token in place of your password.\n ++\n ++---------\n ++[imap]\n ++ folder = \"[Gmail]/Drafts\"\n ++ host = imaps://imap.gmail.com\n ++ user = user@gmail.com\n ++ port = 993\n ++ authmethod = OAUTHBEARER\n ++---------\n ++\n ++Using Outlook's IMAP interface:\n ++\n ++Unlike Gmail, Outlook only supports OAuth2.0 based authentication. Also, it\n ++supports only `XOAUTH2` as the mechanism.\n ++\n ++---------\n ++[imap]\n ++ folder = \"Drafts\"\n ++ host = imaps://outlook.office365.com\n ++ user = user@outlook.com\n ++ port = 993\n ++ authmethod = XOAUTH2\n ++---------\n ++\n + Once the commits are ready to be sent, run the following command:\n + \n + $ git format-patch --cover-letter -M --stdout origin/master | git imap-send\n +@@ Documentation/git-imap-send.adoc: Just make sure to disable line wrapping in the email client (Gmail's web\n + interface will wrap lines no matter what, so you need to use a real\n + IMAP client).\n + \n ++In case you are using OAuth2.0 authentication, it is easier to use credential\n ++helpers to generate tokens. Credential helpers suggested in\n ++linkgit:git-send-email[1] can be used for `git imap-send` as well.\n ++\n + CAUTION\n + -------\n + It is still your responsibility to make sure that the email message\n \n ## imap-send.c ##\n -@@\n +@@ imap-send.c: enum CAPABILITY {\n + \tLITERALPLUS,\n + \tNAMESPACE,\n + \tSTARTTLS,\n +-\tAUTH_CRAM_MD5\n ++\tAUTH_CRAM_MD5,\n ++\tAUTH_OAUTHBEARER,\n ++\tAUTH_XOAUTH2\n + };\n \n - static int verbosity;\n - static int use_curl = USE_CURL_DEFAULT;\n -+static char *opt_folder = NULL;\n + static const char *cap_list[] = {\n +@@ imap-send.c: static const char *cap_list[] = {\n + \t\"NAMESPACE\",\n + \t\"STARTTLS\",\n + \t\"AUTH=CRAM-MD5\",\n ++\t\"AUTH=OAUTHBEARER\",\n ++\t\"AUTH=XOAUTH2\",\n + };\n \n - static const char * const imap_send_usage[] = { \"git imap-send [-v] [-q] [--[no-]curl] < \", NULL };\n + #define RESP_OK 0\n +@@ imap-send.c: static char *cram(const char *challenge_64, const char *user, const char *pass)\n + \treturn (char *)response_64;\n + }\n \n - static struct option imap_send_options[] = {\n - \tOPT__VERBOSITY(&verbosity),\n - \tOPT_BOOL(0, \"curl\", &use_curl, \"use libcurl to communicate with the IMAP server\"),\n -+\tOPT_STRING('f', \"folder\", &opt_folder, \"folder\", \"specify the IMAP folder\"),\n - \tOPT_END()\n - };\n ++static char *oauthbearer_base64(const char *user, const char *access_token)\n ++{\n ++\tint raw_len, b64_len;\n ++\tchar *raw, *b64;\n ++\n ++\t/* Compose the OAUTHBEARER string\n ++\t *\n ++\t * \"n,a=\" {User} \",^Ahost=\" {Host} \"^Aport=\" {Port} \"^Aauth=Bearer \" {Access Token} \"^A^A\n ++\t *\n ++\t * The first part `n,a=\" {User} \",` is the gs2 header described in RFC5801.\n ++\t * * gs2-cb-flag `n` -> client does not support CB\n ++\t * * gs2-authzid `a=\" {User} \"`\n ++\t *\n ++\t * The second part are key value pairs containing host, port and auth as\n ++\t * described in RFC7628.\n ++\t *\n ++\t * https://datatracker.ietf.org/doc/html/rfc5801\n ++\t * https://datatracker.ietf.org/doc/html/rfc7628\n ++\t */\n ++\traw_len = strlen(user) + strlen(access_token) + 20;\n ++\traw = xmallocz(raw_len + 1);\n ++\tsnprintf(raw, raw_len + 1, \"n,a=%s,\\001auth=Bearer %s\\001\\001\", user, access_token);\n ++\n ++\t/* Base64 encode */\n ++\tb64 = xmallocz(ENCODED_SIZE(strlen(raw)));\n ++\tb64_len = EVP_EncodeBlock((unsigned char *)b64, (unsigned char *)raw, strlen(raw));\n ++\tfree(raw);\n ++\n ++\tif (b64_len < 0) {\n ++\t\tfree(b64);\n ++\t\treturn NULL;\n ++\t}\n ++\treturn b64;\n ++}\n ++\n ++static char *xoauth2_base64(const char *user, const char *access_token)\n ++{\n ++\tint raw_len, b64_len;\n ++\tchar *raw, *b64;\n ++\n ++\t/* Compose the XOAUTH2 string\n ++\t * \"user=\" {User} \"^Aauth=Bearer \" {Access Token} \"^A^A\"\n ++\t * https://developers.google.com/workspace/gmail/imap/xoauth2-protocol#initial_client_response\n ++\t */\n ++\traw_len = strlen(user) + strlen(access_token) + 20;\n ++\traw = xmallocz(raw_len + 1);\n ++\tsnprintf(raw, raw_len + 1, \"user=%s\\001auth=Bearer %s\\001\\001\", user, access_token);\n ++\n ++\t/* Base64 encode */\n ++\tb64 = xmallocz(ENCODED_SIZE(strlen(raw)));\n ++\tb64_len = EVP_EncodeBlock((unsigned char *)b64, (unsigned char *)raw, strlen(raw));\n ++\tfree(raw);\n ++\n ++\tif (b64_len < 0) {\n ++\t\tfree(b64);\n ++\t\treturn NULL;\n ++\t}\n ++\treturn b64;\n ++}\n ++\n + #else\n \n -@@ imap-send.c: int cmd_main(int argc, const char **argv)\n + static char *cram(const char *challenge_64 UNUSED,\n +@@ imap-send.c: static char *cram(const char *challenge_64 UNUSED,\n + \t \"you have to build git-imap-send with OpenSSL library.\");\n + }\n \n - \targc = parse_options(argc, (const char **)argv, \"\", imap_send_options, imap_send_usage, 0);\n ++static char *oauthbearer_base64(const char *user UNUSED,\n ++\t\t const char *access_token UNUSED)\n ++{\n ++\tdie(\"You are trying to use OAUTHBEARER authenticate method \"\n ++\t \"with OpenSSL library, but it's support has not been compiled in.\");\n ++}\n ++\n ++static char *xoauth2_base64(const char *user UNUSED,\n ++\t\t const char *access_token UNUSED)\n ++{\n ++\tdie(\"You are trying to use XOAUTH2 authenticate method \"\n ++\t \"with OpenSSL library, but it's support has not been compiled in.\");\n ++}\n ++\n + #endif\n \n -+\tif (opt_folder) {\n -+\t\tfree(server.folder);\n -+\t\tserver.folder = xstrdup(opt_folder);\n + static int auth_cram_md5(struct imap_store *ctx, const char *prompt)\n +@@ imap-send.c: static int auth_cram_md5(struct imap_store *ctx, const char *prompt)\n + \treturn 0;\n + }\n + \n ++static int auth_oauthbearer(struct imap_store *ctx, const char *prompt UNUSED)\n ++{\n ++\tint ret;\n ++\tchar *b64;\n ++\n ++\tb64 = oauthbearer_base64(ctx->cfg->user, ctx->cfg->pass);\n ++\tif (!b64)\n ++\t\treturn error(\"OAUTHBEARER: base64 encoding failed\");\n ++\n ++\t/* Send the base64-encoded response */\n ++\tret = socket_write(&ctx->imap->buf.sock, b64, strlen(b64));\n ++\tif (ret != (int)strlen(b64)) {\n ++\t\tfree(b64);\n ++\t\treturn error(\"IMAP error: sending OAUTHBEARER response failed\");\n ++\t}\n ++\n ++\tfree(b64);\n ++\treturn 0;\n ++}\n ++\n ++static int auth_xoauth2(struct imap_store *ctx, const char *prompt UNUSED)\n ++{\n ++\tint ret;\n ++\tchar *b64;\n ++\n ++\tb64 = xoauth2_base64(ctx->cfg->user, ctx->cfg->pass);\n ++\tif (!b64)\n ++\t\treturn error(\"XOAUTH2: base64 encoding failed\");\n ++\n ++\t/* Send the base64-encoded response */\n ++\tret = socket_write(&ctx->imap->buf.sock, b64, strlen(b64));\n ++\tif (ret != (int)strlen(b64)) {\n ++\t\tfree(b64);\n ++\t\treturn error(\"IMAP error: sending XOAUTH2 response failed\");\n +\t}\n +\n - \tif (argc)\n - \t\tusage_with_options(imap_send_usage, imap_send_options);\n ++\tfree(b64);\n ++\treturn 0;\n ++}\n ++\n + static void server_fill_credential(struct imap_server_conf *srvc, struct credential *cred)\n + {\n + \tif (srvc->user && srvc->pass)\n +@@ imap-send.c: static struct imap_store *imap_open_store(struct imap_server_conf *srvc, const c\n + \t\t\t\t\tfprintf(stderr, \"IMAP error: AUTHENTICATE CRAM-MD5 failed\\n\");\n + \t\t\t\t\tgoto bail;\n + \t\t\t\t}\n ++\t\t\t} else if (!strcmp(srvc->auth_method, \"OAUTHBEARER\")) {\n ++\t\t\t\tif (!CAP(AUTH_OAUTHBEARER)) {\n ++\t\t\t\t\tfprintf(stderr, \"You specified \"\n ++\t\t\t\t\t\t\"OAUTHBEARER as authentication method, \"\n ++\t\t\t\t\t\t\"but %s doesn't support it.\\n\", srvc->host);\n ++\t\t\t\t\tgoto bail;\n ++\t\t\t\t}\n ++\t\t\t\t/* OAUTHBEARER */\n ++\n ++\t\t\t\tmemset(&cb, 0, sizeof(cb));\n ++\t\t\t\tcb.cont = auth_oauthbearer;\n ++\t\t\t\tif (imap_exec(ctx, &cb, \"AUTHENTICATE OAUTHBEARER\") != RESP_OK) {\n ++\t\t\t\t\tfprintf(stderr, \"IMAP error: AUTHENTICATE OAUTHBEARER failed\\n\");\n ++\t\t\t\t\tgoto bail;\n ++\t\t\t\t}\n ++\t\t\t} else if (!strcmp(srvc->auth_method, \"XOAUTH2\")) {\n ++\t\t\t\tif (!CAP(AUTH_XOAUTH2)) {\n ++\t\t\t\t\tfprintf(stderr, \"You specified \"\n ++\t\t\t\t\t\t\"XOAUTH2 as authentication method, \"\n ++\t\t\t\t\t\t\"but %s doesn't support it.\\n\", srvc->host);\n ++\t\t\t\t\tgoto bail;\n ++\t\t\t\t}\n ++\t\t\t\t/* XOAUTH2 */\n ++\n ++\t\t\t\tmemset(&cb, 0, sizeof(cb));\n ++\t\t\t\tcb.cont = auth_xoauth2;\n ++\t\t\t\tif (imap_exec(ctx, &cb, \"AUTHENTICATE XOAUTH2\") != RESP_OK) {\n ++\t\t\t\t\tfprintf(stderr, \"IMAP error: AUTHENTICATE XOAUTH2 failed\\n\");\n ++\t\t\t\t\tgoto bail;\n ++\t\t\t\t}\n + \t\t\t} else {\n + \t\t\t\tfprintf(stderr, \"Unknown authentication method:%s\\n\", srvc->host);\n + \t\t\t\tgoto bail;\n +@@ imap-send.c: static CURL *setup_curl(struct imap_server_conf *srvc, struct credential *cred)\n + \n + \tserver_fill_credential(srvc, cred);\n + \tcurl_easy_setopt(curl, CURLOPT_USERNAME, srvc->user);\n +-\tcurl_easy_setopt(curl, CURLOPT_PASSWORD, srvc->pass);\n ++\n ++\tif (!srvc->auth_method ||\n ++\t strcmp(srvc->auth_method, \"XOAUTH2\") ||\n ++\t strcmp(srvc->auth_method, \"OAUTHBEARER\"))\n ++\t\tcurl_easy_setopt(curl, CURLOPT_PASSWORD, srvc->pass);\n + \n + \tstrbuf_addstr(&path, srvc->use_ssl ? \"imaps://\" : \"imap://\");\n + \tstrbuf_addstr(&path, srvc->host);\n +@@ imap-send.c: static CURL *setup_curl(struct imap_server_conf *srvc, struct credential *cred)\n + \tcurl_easy_setopt(curl, CURLOPT_PORT, srvc->port);\n + \n + \tif (srvc->auth_method) {\n +-\t\tstruct strbuf auth = STRBUF_INIT;\n +-\t\tstrbuf_addstr(&auth, \"AUTH=\");\n +-\t\tstrbuf_addstr(&auth, srvc->auth_method);\n +-\t\tcurl_easy_setopt(curl, CURLOPT_LOGIN_OPTIONS, auth.buf);\n +-\t\tstrbuf_release(&auth);\n ++\t\tif (!strcmp(srvc->auth_method, \"XOAUTH2\") ||\n ++\t\t !strcmp(srvc->auth_method, \"OAUTHBEARER\")) {\n ++\n ++\t\t\t/* While CURLOPT_XOAUTH2_BEARER looks as if it only supports XOAUTH2,\n ++\t\t\t * upon debugging, it has been found that it is capable of detecting\n ++\t\t\t * the best option out of OAUTHBEARER and XOAUTH2.\n ++\t\t\t */\n ++\t\t\tcurl_easy_setopt(curl, CURLOPT_XOAUTH2_BEARER, srvc->pass);\n ++\t\t} else {\n ++\t\t\tstruct strbuf auth = STRBUF_INIT;\n ++\t\t\tstrbuf_addstr(&auth, \"AUTH=\");\n ++\t\t\tstrbuf_addstr(&auth, srvc->auth_method);\n ++\t\t\tcurl_easy_setopt(curl, CURLOPT_LOGIN_OPTIONS, auth.buf);\n ++\t\t\tstrbuf_release(&auth);\n ++\t\t}\n + \t}\n \n + \tif (!srvc->use_ssl)\n-: ---------- > 3: e3dc19dc49 imap-send: add PLAIN authentication method to OpenSSL\n-: ---------- > 4: 11f7ac1325 imap-send: fix memory leak in case auth_cram_md5 fails\n-: ---------- > 5: f6e7a5498e imap-send: enable specifying the folder using the command line\n2: 245cc89cca = 6: 4769924781 imap-send: enable user to choose between libcurl and openssl using the config\n-- \n2.49.0.windows.1\n\n\n"},{"id":"519070","messageId":"PN3PR01MB95971983DABB391AD64CB60BB867A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"PN3PR01MB95972C400AE59DAB2EB388A5B867A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"Re: [PATCH v5 0/4] docs: update email credential helpers and improve formatting","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-28T10:05:50Z","receivedAt":"2025-05-28T10:05:57Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\nOn 28-05-2025 03:12 pm, Aditya Garg wrote:\n> \n> \n> On 28-05-2025 03:06 pm, Aditya Garg wrote:\n>>\n>>\n>> On 28-05-2025 12:53 pm, Eric Sunshine wrote:\n>>> On Wed, May 28, 2025 at 3:05 AM Aditya Garg wrote:\n>>>> v5: Added a patch to make the purpose of using app password for Gmail\n>>>> more clear in `send-email` documentation.\n>>>>\n>>>> Range-diff:\n>>>> -: ---------- > 1: 2c47cc5396 docs: add credential helper for yahoo and link Google's sendgmail tool\n>>>> -: ---------- > 2: bc1d0471ca docs: improve formatting in git-send-email documentation\n>>>> -: ---------- > 3: b9e41e2492 docs: remove credential helper links for emails from gitcredentials\n>>>> -: ---------- > 4: a6ad7ac810 docs: make the purpose of using app password for Gmail more clear in send-email\n>>>\n>>> Strange range-diff.\n>>\n>> I think because I used git version 2.43. When I compiled my branch with changes, git format-patch over there\n>> had a very different range-diff from this.\n> \n> I get this range-diff with git 2.49\n\nDisregard this message, I just mixed up two different threads.\n"},{"id":"519071","messageId":"PN3PR01MB9597E129D2F97A2AE598C1D5B867A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"PN3PR01MB9597EBE360893FA638B17952B867A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"Re: [PATCH v5 0/4] docs: update email credential helpers and improve formatting","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-28T10:10:21Z","receivedAt":"2025-05-28T10:10:29Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\nOn 28-05-2025 03:06 pm, Aditya Garg wrote:\n> \n> \n> On 28-05-2025 12:53 pm, Eric Sunshine wrote:\n>> On Wed, May 28, 2025 at 3:05 AM Aditya Garg wrote:\n>>> v5: Added a patch to make the purpose of using app password for Gmail\n>>> more clear in `send-email` documentation.\n>>>\n>>> Range-diff:\n>>> -: ---------- > 1: 2c47cc5396 docs: add credential helper for yahoo and link Google's sendgmail tool\n>>> -: ---------- > 2: bc1d0471ca docs: improve formatting in git-send-email documentation\n>>> -: ---------- > 3: b9e41e2492 docs: remove credential helper links for emails from gitcredentials\n>>> -: ---------- > 4: a6ad7ac810 docs: make the purpose of using app password for Gmail more clear in send-email\n>>\n>> Strange range-diff.\n> \n> I think because I used git version 2.43. When I compiled my branch with changes, git format-patch over there\n> had a very different range-diff from this.\n\nThis is the one from Git 2.49\n\nRange-diff:\n2: 72b3cd1bfb ! 1: 2c47cc5396 send-email: show the new message id assigned by outlook in the logs\n @@ Metadata\n Author: Aditya Garg \n \n ## Commit message ##\n - send-email: show the new message id assigned by outlook in the logs\n + docs: add credential helper for yahoo and link Google's sendgmail tool\n \n - Whenever an email is sent, send-email shows a log at last, which\n - contains all the headers of the email that were received by the\n - receipients.\n -\n - In case outlook changes the Message-ID, a log for the same is shown to\n - the user, but that change is not reflected when the log containing all\n - the headers is displayed. Here is an example of the log that is shown\n - when outlook changes the Message-ID:\n -\n - Outlook reassigned Message-ID to: \n - OK. Log says:\n - Server: smtp.office365.com\n - MAIL FROM:\n - RCPT TO:\n - From: Aditya Garg \n - To: negahe7142@nomrista.com\n - Subject: [PATCH] send-email: show the new message id assigned by outlook in the logs\n - Date: Mon, 26 May 2025 20:28:36 +0530\n - Message-ID: <20250526145836.4825-1-gargaditya08@live.com>\n - X-Mailer: git-send-email @GIT_VERSION@\n - MIME-Version: 1.0\n - Content-Transfer-Encoding: 8bit\n -\n - Result: 250\n -\n - This patch fixes this by modifying the $header variable, which is\n - responsible for showing the logs at the end. Also, the log which states\n - that the Message-ID has been changed will now be shown only when\n - smtp-debug is enabled, since the main log having all of the headers is\n - anyways displaying the new Message-ID. It should look like this after\n - this patch:\n -\n - OK. Log says:\n - Server: smtp.office365.com\n - MAIL FROM:\n - RCPT TO:\n - From: Aditya Garg \n - To: negahe7142@nomrista.com\n - Subject: [PATCH] send-email: show the new message id assigned by outlook in the logs\n - Date: Mon, 26 May 2025 20:29:22 +0530\n - Message-ID: \n - X-Mailer: git-send-email @GIT_VERSION@\n - MIME-Version: 1.0\n - Content-Transfer-Encoding: 8bit\n -\n - Result: 250\n + This commit links `git-credential-yahoo` as a credential helper for\n + Yahoo accounts. Also, Google's `sendgmail` tool has been linked as an\n + alternative method for sending emails through Gmail.\n \n Signed-off-by: Aditya Garg \n \n - ## git-send-email.perl ##\n -@@ git-send-email.perl: sub send_message {\n - \t\tif (is_outlook($smtp_server)) {\n - \t\t\tif ($smtp->message =~ /<([^>]+)>/) {\n - \t\t\t\t$message_id = \"<$1>\";\n --\t\t\t\tprintf __(\"Outlook reassigned Message-ID to: %s\\n\"), $message_id;\n -+\t\t\t\t# Replace the original Message-ID in $header with the new one\n -+\t\t\t\t$header =~ s/^(Message-ID:\\s*).*\\n/${1}$message_id\\n/m;\n -+\t\t\t\tprintf __(\"Outlook reassigned Message-ID to: %s\\n\"), $message_id if $smtp->debug;\n - \t\t\t} else {\n - \t\t\t\twarn __(\"Warning: Could not retrieve Message-ID from server response.\\n\");\n - \t\t\t}\n + ## Documentation/git-send-email.adoc ##\n +@@ Documentation/git-send-email.adoc: settings:\n + \tsmtpAuth = OAUTHBEARER\n + ----\n + \n ++Alternatively, you can use a tool developed by Google known as\n ++https://github.com/google/gmail-oauth2-tools/tree/master/go/sendgmail[sendgmail]\n ++to send emails using `git send-email`.\n ++\n + Use Microsoft Outlook as the SMTP Server\n + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n + Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.\n +@@ Documentation/git-send-email.adoc: next time.\n + \n + If you are using OAuth2.0 authentication, you need to use an access token in\n + place of a password when prompted. Various OAuth2.0 token generators are\n +-available online. Community maintained credential helpers for Gmail and Outlook\n +-are also available:\n ++available online. Community maintained credential helpers are also available:\n + \n + \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail]\n + \t (cross platform, dedicated helper for authenticating Gmail accounts)\n +@@ Documentation/git-send-email.adoc: are also available:\n + \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook]\n + \t (cross platform, dedicated helper for authenticating Microsoft Outlook accounts)\n + \n ++\t- https://github.com/AdityaGarg8/git-credential-email[git-credential-yahoo]\n ++\t (cross platform, dedicated helper for authenticating Yahoo accounts)\n ++\n + You can also see linkgit:gitcredentials[7] for more OAuth based authentication\n + helpers.\n + \n1: 63addf9d9b ! 2: bc1d0471ca send-email: fix bug resulting in increased message number if a message is edited\n @@ Metadata\n Author: Aditya Garg \n \n ## Commit message ##\n - send-email: fix bug resulting in increased message number if a message is edited\n + docs: improve formatting in git-send-email documentation\n \n - Whenever we send a thread of emails using send-email, a message number\n - is internally assigned to each email. This number is used to track the\n - order of the emails in the thread. Whenever a new message is processed\n - in a thread, the current script logic increases the message number by\n - one, which is intended.\n + The current documentation for git-send-email had an inconsistent use of\n + \"\", ``, and '' for quoting. This commit improves the formatting by\n + using the same style throughout the documentation.\n \n - But, if a message is edited and then resent, its message number again\n - gets increased. This is because the script uses the same logic to\n - process the edited message, which is uses the send the next message.\n + Also, at some places, minor grammatical errors were fixed, and some\n + non existent links were removed.\n \n - This minor bug is usually harmless unless some special situations arise.\n - One such situation is when the first message in a thread is edited\n - and resent, and an `--in-reply-to` argument is also passed to send-email.\n - In this case if the user has chosen shallow threading, the threading\n - does not work as expected, and all messaged become as replies to the\n - Message-ID specified in the `--in-reply-to` argument.\n -\n - The reason for this bug is hidden in the code for threading itself.\n -\n - if ($thread) {\n - if ($message_was_sent &&\n - ($chain_reply_to || !defined $in_reply_to || length($in_reply_to) == 0 ||\n - $message_num == 1)) {\n - $in_reply_to = $message_id;\n - if (length $references > 0) {\n - $references .= \"\\n $message_id\";\n - } else {\n - $references = \"$message_id\";\n - }\n - }\n - }\n -\n - Here $message_num is the current message number, and $in_reply_to is\n - the Message-ID of the message to which the current message is a reply.\n - In case `--in-reply-to` is specified, the `$in_reply_to` variable\n - is set to the value of the `--in-reply-to` argument.\n -\n - Whenever this whole set of conditions is true, the script sets the\n - `$in_reply_to` variable to the current message's ID. This is done to\n - ensure that the next message in the thread is a reply to this message.\n -\n - In case we specify an `--in-reply-to` argument, and have shallow\n - threading, the only condition that can make this true is\n - `$message_num == 1`, which is true for the first message in a thread.\n - Thus the $in_reply_to variable gets set to the first message's ID.\n - For subsequent messages, the `$message_num` variable is always\n - greater than 1, and the whole set of conditions is false, and thus the\n - $in_reply_to variable remains as the first message's ID. This is what\n - we expect in shallow threading. But, in case the user edits the first\n - message and resends it, the `$message_num` variable gets increased by 1,\n - and thus the condition `$message_num == 1` becomes false. This means\n - that the `$in_reply_to` variable is not set to the first message's ID,\n - and thus the next message in the thread is not a reply to the first\n - message, but to the `--in-reply-to` argument, effectively breaking\n - the threading.\n -\n - In case the user does not specify an `--in-reply-to` argument, the\n - !defined $in_reply_to condition is true, and thus the `$in_reply_to`\n - variable is set to the first message's ID, and the threading works\n - as expected, irrespective of what the message number is.\n -\n - Just like $message_num, $message_id_serial variable also increases by 1\n - whenever a new message is sent. This variable displays the message\n - number is the Message-ID of the email.\n -\n - So, in order to fix this bug, we need to ensure that the $message_num\n - variable is not increased by 1 when a message is edited and resent.\n - We do this by decreasing the $message_num and $message_id_serial\n - variable by 1 whenever the request to edit a message is received. This\n - way, the next message in the thread will have the same message number as\n - the edited message, and thus the threading will work as expected.\n -\n - The same logic has also been applied in case the user drops a single\n - message from the thread by choosing the \"[n]o\" option during\n - confirmation. By doing this, the next message in the thread is assigned\n - the message number of the dropped message, and thus the threading\n - works as expected.\n + Finally, the cpan links of necessary perl modules have been added to\n + make their installation easier.\n \n Signed-off-by: Aditya Garg \n \n - ## git-send-email.perl ##\n -@@ git-send-email.perl: sub send_message {\n - \t\t default => $ask_default);\n - \t\tdie __(\"Send this email reply required\") unless defined $_;\n - \t\tif (/^n/i) {\n -+\t\t\t# If we are skipping a message, we should make sure that\n -+\t\t\t# the next message is treated as the successor to the\n -+\t\t\t# previously sent message, and not the skipped message.\n -+\t\t\t$message_num--;\n -+\t\t\t$message_id_serial--;\n - \t\t\treturn 0;\n - \t\t} elsif (/^e/i) {\n -+\t\t\t# Since the same message will be sent again, we need to\n -+\t\t\t# decrement the message number to the previous message.\n -+\t\t\t# Otherwise, the edited message will be treated as a\n -+\t\t\t# different message sent after the original non-edited\n -+\t\t\t# message.\n -+\t\t\t$message_num--;\n -+\t\t\t$message_id_serial--;\n - \t\t\treturn -1;\n - \t\t} elsif (/^q/i) {\n - \t\t\tcleanup_compose_files();\n + ## Documentation/config/sendemail.adoc ##\n +@@ Documentation/config/sendemail.adoc: sendemail..*::\n + \t`sendemail.identity`.\n + \n + sendemail.multiEdit::\n +-\tIf true (default), a single editor instance will be spawned to edit\n ++\tIf `true` (default), a single editor instance will be spawned to edit\n + \tfiles you have to edit (patches when `--annotate` is used, and the\n +-\tsummary when `--compose` is used). If false, files will be edited one\n ++\tsummary when `--compose` is used). If `false`, files will be edited one\n + \tafter the other, spawning a new editor each time.\n + \n + sendemail.confirm::\n +@@ Documentation/config/sendemail.adoc: sendemail.signedOffCc (deprecated)::\n + \n + sendemail.smtpBatchSize::\n + \tNumber of messages to be sent per connection, after that a relogin\n +-\twill happen. If the value is 0 or undefined, send all messages in\n ++\twill happen. If the value is `0` or undefined, send all messages in\n + \tone connection.\n + \tSee also the `--batch-size` option of linkgit:git-send-email[1].\n + \n +@@ Documentation/config/sendemail.adoc: sendemail.smtpReloginDelay::\n + \n + sendemail.forbidSendmailVariables::\n + \tTo avoid common misconfiguration mistakes, linkgit:git-send-email[1]\n +-\twill abort with a warning if any configuration options for \"sendmail\"\n ++\twill abort with a warning if any configuration options for `sendmail`\n + \texist. Set this variable to bypass the check.\n +\n + ## Documentation/git-send-email.adoc ##\n +@@ Documentation/git-send-email.adoc: Takes the patches given on the command line and emails them out.\n + Patches can be specified as files, directories (which will send all\n + files in the directory), or directly as a revision list. In the\n + last case, any format accepted by linkgit:git-format-patch[1] can\n +-be passed to git send-email, as well as options understood by\n ++be passed to `git send-email`, as well as options understood by\n + linkgit:git-format-patch[1].\n + \n + The header of the email is configurable via command-line options. If not\n +@@ Documentation/git-send-email.adoc: There are two formats accepted for patch files:\n + This is what linkgit:git-format-patch[1] generates. Most headers and MIME\n + formatting are ignored.\n + \n +-2. The original format used by Greg Kroah-Hartman's 'send_lots_of_email.pl'\n ++2. The original format used by Greg Kroah-Hartman's `send_lots_of_email.pl`\n + script\n + +\n +-This format expects the first line of the file to contain the \"Cc:\" value\n +-and the \"Subject:\" of the message as the second line.\n ++This format expects the first line of the file to contain the 'Cc:' value\n ++and the 'Subject:' of the message as the second line.\n + \n + \n + OPTIONS\n +@@ Documentation/git-send-email.adoc: Composing\n + \t`sendemail.multiEdit`.\n + \n + --bcc=
,...::\n +-\tSpecify a \"Bcc:\" value for each email. Default is the value of\n ++\tSpecify a 'Bcc:' value for each email. Default is the value of\n + \t`sendemail.bcc`.\n + +\n + This option may be specified multiple times.\n + \n + --cc=
,...::\n +-\tSpecify a starting \"Cc:\" value for each email.\n ++\tSpecify a starting 'Cc:' value for each email.\n + \tDefault is the value of `sendemail.cc`.\n + +\n + This option may be specified multiple times.\n +@@ Documentation/git-send-email.adoc: This option may be specified multiple times.\n + \tInvoke a text editor (see GIT_EDITOR in linkgit:git-var[1])\n + \tto edit an introductory message for the patch series.\n + +\n +-When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n +-Subject, Reply-To, and In-Reply-To headers specified in the message. If\n +-the body of the message (what you type after the headers and a blank\n +-line) only contains blank (or Git: prefixed) lines, the summary won't be\n ++When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n ++'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n ++message. If the body of the message (what you type after the headers and a\n ++blank line) only contains blank (or Git: prefixed) lines, the summary won't be\n + sent, but the headers mentioned above will be used unless they are\n + removed.\n + +\n +-Missing From or In-Reply-To headers will be prompted for.\n ++Missing 'From' or 'In-Reply-To' headers will be prompted for.\n + +\n + See the CONFIGURATION section for `sendemail.multiEdit`.\n + \n +@@ Documentation/git-send-email.adoc: See the CONFIGURATION section for `sendemail.multiEdit`.\n + \tthe value of the `sendemail.from` configuration option is used. If\n + \tneither the command-line option nor `sendemail.from` are set, then the\n + \tuser will be prompted for the value. The default for the prompt will be\n +-\tthe value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not\n +-\tset, as returned by \"git var -l\".\n ++\tthe value of `GIT_AUTHOR_IDENT`, or `GIT_COMMITTER_IDENT` if that is not\n ++\tset, as returned by `git var -l`.\n + \n + --reply-to=
::\n + \tSpecify the address where replies from recipients should go to.\n + \tUse this if replies to messages should go to another address than what\n +-\tis specified with the --from parameter.\n ++\tis specified with the `--from` parameter.\n + \n + --in-reply-to=::\n + \tMake the first mail (or all the mails with `--no-thread`) appear as a\n +@@ Documentation/git-send-email.adoc: illustration below where `[PATCH v2 0/3]` is in reply to `[PATCH 0/2]`:\n + [PATCH v2 2/3] New tests\n + [PATCH v2 3/3] Implementation\n + +\n +-Only necessary if --compose is also set. If --compose\n ++Only necessary if `--compose` is also set. If `--compose`\n + is not set, this will be prompted for.\n + \n + --[no-]outlook-id-fix::\n + \tMicrosoft Outlook SMTP servers discard the Message-ID sent via email and\n + \tassign a new random Message-ID, thus breaking threads.\n + +\n +-With `--outlook-id-fix`, 'git send-email' uses a mechanism specific to\n ++With `--outlook-id-fix`, `git send-email` uses a mechanism specific to\n + Outlook servers to learn the Message-ID the server assigned to fix the\n + threading. Use it only when you know that the server reports the\n + rewritten Message-ID the same way as Outlook servers do.\n +@@ Documentation/git-send-email.adoc: to 'smtp.office365.com' or 'smtp-mail.outlook.com'. Use\n + \n + --subject=::\n + \tSpecify the initial subject of the email thread.\n +-\tOnly necessary if --compose is also set. If --compose\n ++\tOnly necessary if `--compose` is also set. If `--compose`\n + \tis not set, this will be prompted for.\n + \n + --to=
,...::\n + \tSpecify the primary recipient of the emails generated. Generally, this\n + \twill be the upstream maintainer of the project involved. Default is the\n + \tvalue of the `sendemail.to` configuration value; if that is unspecified,\n +-\tand --to-cmd is not specified, this will be prompted for.\n ++\tand `--to-cmd` is not specified, this will be prompted for.\n + +\n + This option may be specified multiple times.\n + \n +@@ Documentation/git-send-email.adoc: This option may be specified multiple times.\n + \tWhen encountering a non-ASCII message or subject that does not\n + \tdeclare its encoding, add headers/quoting to indicate it is\n + \tencoded in . Default is the value of the\n +-\t'sendemail.assume8bitEncoding'; if that is unspecified, this\n ++\t`sendemail.assume8bitEncoding`; if that is unspecified, this\n + \twill be prompted for if any non-ASCII files are encountered.\n + +\n + Note that no attempts whatsoever are made to validate the encoding.\n + \n + --compose-encoding=::\n + \tSpecify encoding of compose message. Default is the value of the\n +-\t'sendemail.composeEncoding'; if that is unspecified, UTF-8 is assumed.\n ++\t`sendemail.composeEncoding`; if that is unspecified, UTF-8 is assumed.\n + \n + --transfer-encoding=(7bit|8bit|quoted-printable|base64|auto)::\n + \tSpecify the transfer encoding to be used to send the message over SMTP.\n +-\t7bit will fail upon encountering a non-ASCII message. quoted-printable\n ++\t'7bit' will fail upon encountering a non-ASCII message. 'quoted-printable'\n + \tcan be useful when the repository contains files that contain carriage\n +-\treturns, but makes the raw patch email file (as saved from a MUA) much\n +-\tharder to inspect manually. base64 is even more fool proof, but also\n +-\teven more opaque. auto will use 8bit when possible, and quoted-printable\n +-\totherwise.\n ++\treturns, but makes the raw patch email file (as saved from an MUA) much\n ++\tharder to inspect manually. 'base64' is even more fool proof, but also\n ++\teven more opaque. 'auto' will use '8bit' when possible, and\n ++\t'quoted-printable' otherwise.\n + +\n + Default is the value of the `sendemail.transferEncoding` configuration\n +-value; if that is unspecified, default to `auto`.\n ++value; if that is unspecified, default to 'auto'.\n + \n + --xmailer::\n + --no-xmailer::\n +-\tAdd (or prevent adding) the \"X-Mailer:\" header. By default,\n ++\tAdd (or prevent adding) the 'X-Mailer:' header. By default,\n + \tthe header is added, but it can be turned off by setting the\n + \t`sendemail.xmailer` configuration variable to `false`.\n + \n +@@ Documentation/git-send-email.adoc: Sending\n + \tSpecify the envelope sender used to send the emails.\n + \tThis is useful if your default address is not the address that is\n + \tsubscribed to a list. In order to use the 'From' address, set the\n +-\tvalue to \"auto\". If you use the sendmail binary, you must have\n +-\tsuitable privileges for the -f parameter. Default is the value of the\n ++\tvalue to `auto`. If you use the `sendmail` binary, you must have\n ++\tsuitable privileges for the `-f` parameter. Default is the value of the\n + \t`sendemail.envelopeSender` configuration variable; if that is\n + \tunspecified, choosing the envelope sender is left to your MTA.\n + \n +@@ Documentation/git-send-email.adoc: Sending\n + \tbe sendmail-like; specifically, it must support the `-i` option.\n + \tThe command will be executed in the shell if necessary. Default\n + \tis the value of `sendemail.sendmailCmd`. If unspecified, and if\n +-\t--smtp-server is also unspecified, git-send-email will search\n +-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH.\n ++\t`--smtp-server` is also unspecified, `git send-email` will search\n ++\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH`.\n + \n + --smtp-encryption=::\n + \tSpecify in what way encrypting begins for the SMTP connection.\n +@@ Documentation/git-send-email.adoc: Sending\n + --smtp-domain=::\n + \tSpecifies the Fully Qualified Domain Name (FQDN) used in the\n + \tHELO/EHLO command to the SMTP server. Some servers require the\n +-\tFQDN to match your IP address. If not set, git send-email attempts\n ++\tFQDN to match your IP address. If not set, `git send-email` attempts\n + \tto determine your FQDN automatically. Default is the value of\n + \t`sendemail.smtpDomain`.\n + \n +@@ Documentation/git-send-email.adoc: $ git send-email --smtp-auth=\"PLAIN LOGIN GSSAPI\" ...\n + +\n + If at least one of the specified mechanisms matches the ones advertised by the\n + SMTP server and if it is supported by the utilized SASL library, the mechanism\n +-is used for authentication. If neither 'sendemail.smtpAuth' nor `--smtp-auth`\n ++is used for authentication. If neither `sendemail.smtpAuth` nor `--smtp-auth`\n + is specified, all mechanisms supported by the SASL library can be used. The\n +-special value 'none' maybe specified to completely disable authentication\n +-independently of `--smtp-user`\n ++special value `none` maybe specified to completely disable authentication\n ++independently of `--smtp-user`.\n + \n + --smtp-pass[=]::\n + \tPassword for SMTP-AUTH. The argument is optional: If no\n +@@ Documentation/git-send-email.adoc: Furthermore, passwords need not be specified in configuration files\n + or on the command line. If a username has been specified (with\n + `--smtp-user` or a `sendemail.smtpUser`), but no password has been\n + specified (with `--smtp-pass` or `sendemail.smtpPass`), then\n +-a password is obtained using 'git-credential'.\n ++a password is obtained using linkgit:git-credential[1].\n + \n + --no-smtp-auth::\n +-\tDisable SMTP authentication. Short hand for `--smtp-auth=none`\n ++\tDisable SMTP authentication. Short hand for `--smtp-auth=none`.\n + \n + --smtp-server=::\n + \tIf set, specifies the outgoing SMTP server to use (e.g.\n + \t`smtp.example.com` or a raw IP address). If unspecified, and if\n + \t`--sendmail-cmd` is also unspecified, the default is to search\n +-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH if such a\n ++\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH` if such a\n + \tprogram is available, falling back to `localhost` otherwise.\n + +\n + For backward compatibility, this option can also specify a full pathname\n +@@ Documentation/git-send-email.adoc: instead.\n + \tSpecifies a port different from the default port (SMTP\n + \tservers typically listen to smtp port 25, but may also listen to\n + \tsubmission port 587, or the common SSL smtp port 465);\n +-\tsymbolic port names (e.g. \"submission\" instead of 587)\n ++\tsymbolic port names (e.g. `submission` instead of 587)\n + \tare also accepted. The port can also be set with the\n + \t`sendemail.smtpServerPort` configuration variable.\n + \n +@@ Documentation/git-send-email.adoc: instead.\n + \tDefault value can be specified by the `sendemail.smtpServerOption`\n + \tconfiguration option.\n + +\n +-The --smtp-server-option option must be repeated for each option you want\n ++The `--smtp-server-option` option must be repeated for each option you want\n + to pass to the server. Likewise, different lines in the configuration files\n + must be used for each option.\n + \n +@@ Documentation/git-send-email.adoc: must be used for each option.\n + --smtp-ssl-cert-path::\n + \tPath to a store of trusted CA certificates for SMTP SSL/TLS\n + \tcertificate validation (either a directory that has been processed\n +-\tby 'c_rehash', or a single file containing one or more PEM format\n +-\tcertificates concatenated together: see verify(1) -CAfile and\n +-\t-CApath for more information on these). Set it to an empty string\n ++\tby `c_rehash`, or a single file containing one or more PEM format\n ++\tcertificates concatenated together). Set it to an empty string\n + \tto disable certificate verification. Defaults to the value of the\n + \t`sendemail.smtpSSLCertPath` configuration variable, if set, or the\n + \tbacking SSL library's compiled-in default otherwise (which should\n +@@ Documentation/git-send-email.adoc: must be used for each option.\n + \tconnection and authentication problems.\n + \n + --batch-size=::\n +-\tSome email servers (e.g. smtp.163.com) limit the number emails to be\n ++\tSome email servers (e.g. 'smtp.163.com') limit the number of emails to be\n + \tsent per session (connection) and this will lead to a failure when\n + \tsending many messages. With this option, send-email will disconnect after\n +-\tsending $ messages and wait for a few seconds (see --relogin-delay)\n +-\tand reconnect, to work around such a limit. You may want to\n +-\tuse some form of credential helper to avoid having to retype\n +-\tyour password every time this happens. Defaults to the\n ++\tsending `$` messages and wait for a few seconds\n ++\t(see `--relogin-delay`) and reconnect, to work around such a limit.\n ++\tYou may want to use some form of credential helper to avoid having to\n ++\tretype your password every time this happens. Defaults to the\n + \t`sendemail.smtpBatchSize` configuration variable.\n + \n + --relogin-delay=::\n +-\tWaiting $ seconds before reconnecting to SMTP server. Used together\n +-\twith --batch-size option. Defaults to the `sendemail.smtpReloginDelay`\n ++\tWaiting `$` seconds before reconnecting to SMTP server. Used together\n ++\twith `--batch-size` option. Defaults to the `sendemail.smtpReloginDelay`\n + \tconfiguration variable.\n + \n + Automating\n +@@ Documentation/git-send-email.adoc: Automating\n + --no-to::\n + --no-cc::\n + --no-bcc::\n +-\tClears any list of \"To:\", \"Cc:\", \"Bcc:\" addresses previously\n ++\tClears any list of 'To:', 'Cc:', 'Bcc:' addresses previously\n + \tset via config.\n + \n + --no-identity::\n +@@ Documentation/git-send-email.adoc: Automating\n + \n + --to-cmd=::\n + \tSpecify a command to execute once per patch file which\n +-\tshould generate patch file specific \"To:\" entries.\n ++\tshould generate patch file specific 'To:' entries.\n + \tOutput of this command must be single email address per line.\n +-\tDefault is the value of 'sendemail.toCmd' configuration value.\n ++\tDefault is the value of `sendemail.toCmd` configuration value.\n + \n + --cc-cmd=::\n + \tSpecify a command to execute once per patch file which\n +-\tshould generate patch file specific \"Cc:\" entries.\n ++\tshould generate patch file specific 'Cc:' entries.\n + \tOutput of this command must be single email address per line.\n + \tDefault is the value of `sendemail.ccCmd` configuration value.\n + \n +@@ Documentation/git-send-email.adoc: Automating\n + \tSpecify a command that is executed once per outgoing message\n + \tand output RFC 2822 style header lines to be inserted into\n + \tthem. When the `sendemail.headerCmd` configuration variable is\n +-\tset, its value is always used. When --header-cmd is provided\n ++\tset, its value is always used. When `--header-cmd` is provided\n + \tat the command line, its value takes precedence over the\n + \t`sendemail.headerCmd` configuration variable.\n + \n +@@ Documentation/git-send-email.adoc: Automating\n + \n + --[no-]chain-reply-to::\n + \tIf this is set, each email will be sent as a reply to the previous\n +-\temail sent. If disabled with \"--no-chain-reply-to\", all emails after\n ++\temail sent. If disabled with `--no-chain-reply-to`, all emails after\n + \tthe first will be sent as replies to the first email sent. When using\n + \tthis, it is recommended that the first file given be an overview of the\n + \tentire patch series. Disabled by default, but the `sendemail.chainReplyTo`\n +@@ Documentation/git-send-email.adoc: Automating\n + \tthe value of `sendemail.identity`.\n + \n + --[no-]signed-off-by-cc::\n +-\tIf this is set, add emails found in the `Signed-off-by` trailer or Cc: lines to the\n +-\tcc list. Default is the value of `sendemail.signedOffByCc` configuration\n +-\tvalue; if that is unspecified, default to --signed-off-by-cc.\n ++\tIf this is set, add emails found in the `Signed-off-by` trailer or 'Cc:'\n ++\tlines to the cc list. Default is the value of `sendemail.signedOffByCc`\n ++\tconfiguration value; if that is unspecified, default to\n ++\t`--signed-off-by-cc`.\n + \n + --[no-]cc-cover::\n +-\tIf this is set, emails found in Cc: headers in the first patch of\n ++\tIf this is set, emails found in 'Cc:' headers in the first patch of\n + \tthe series (typically the cover letter) are added to the cc list\n +-\tfor each email set. Default is the value of 'sendemail.ccCover'\n +-\tconfiguration value; if that is unspecified, default to --no-cc-cover.\n ++\tfor each email set. Default is the value of `sendemail.ccCover`\n ++\tconfiguration value; if that is unspecified, default to `--no-cc-cover`.\n + \n + --[no-]to-cover::\n +-\tIf this is set, emails found in To: headers in the first patch of\n ++\tIf this is set, emails found in 'To:' headers in the first patch of\n + \tthe series (typically the cover letter) are added to the to list\n +-\tfor each email set. Default is the value of 'sendemail.toCover'\n +-\tconfiguration value; if that is unspecified, default to --no-to-cover.\n ++\tfor each email set. Default is the value of `sendemail.toCover`\n ++\tconfiguration value; if that is unspecified, default to `--no-to-cover`.\n + \n + --suppress-cc=::\n + \tSpecify an additional category of recipients to suppress the\n +@@ Documentation/git-send-email.adoc: Automating\n + --\n + +\n + Default is the value of `sendemail.suppressCc` configuration value; if\n +-that is unspecified, default to 'self' if --suppress-from is\n +-specified, as well as 'body' if --no-signed-off-cc is specified.\n ++that is unspecified, default to 'self' if `--suppress-from` is\n ++specified, as well as 'body' if `--no-signed-off-cc` is specified.\n + \n + --[no-]suppress-from::\n +-\tIf this is set, do not add the From: address to the cc: list.\n ++\tIf this is set, do not add the 'From:' address to the 'Cc:' list.\n + \tDefault is the value of `sendemail.suppressFrom` configuration\n +-\tvalue; if that is unspecified, default to --no-suppress-from.\n ++\tvalue; if that is unspecified, default to `--no-suppress-from`.\n + \n + --[no-]thread::\n +-\tIf this is set, the In-Reply-To and References headers will be\n ++\tIf this is set, the 'In-Reply-To' and 'References' headers will be\n + \tadded to each email sent. Whether each mail refers to the\n +-\tprevious email (`deep` threading per 'git format-patch'\n ++\tprevious email (`deep` threading per `git format-patch`\n + \twording) or to the first email (`shallow` threading) is\n +-\tgoverned by \"--[no-]chain-reply-to\".\n ++\tgoverned by `--[no-]chain-reply-to`.\n + +\n +-If disabled with \"--no-thread\", those headers will not be added\n +-(unless specified with --in-reply-to). Default is the value of the\n ++If disabled with `--no-thread`, those headers will not be added\n ++(unless specified with `--in-reply-to`). Default is the value of the\n + `sendemail.thread` configuration value; if that is unspecified,\n +-default to --thread.\n ++default to `--thread`.\n + +\n + It is up to the user to ensure that no In-Reply-To header already\n +-exists when 'git send-email' is asked to add it (especially note that\n +-'git format-patch' can be configured to do the threading itself).\n ++exists when `git send-email` is asked to add it (especially note that\n ++`git format-patch` can be configured to do the threading itself).\n + Failure to do so may not produce the expected result in the\n + recipient's MUA.\n + \n + --[no-]mailmap::\n + \tUse the mailmap file (see linkgit:gitmailmap[5]) to map all\n + \taddresses to their canonical real name and email address. Additional\n +-\tmailmap data specific to git-send-email may be provided using the\n ++\tmailmap data specific to `git send-email` may be provided using the\n + \t`sendemail.mailmap.file` or `sendemail.mailmap.blob` configuration\n + \tvalues. Defaults to `sendemail.mailmap`.\n + \n +@@ Documentation/git-send-email.adoc: Administering\n + \tConfirm just before sending:\n + +\n + --\n +-- 'always' will always confirm before sending\n +-- 'never' will never confirm before sending\n ++- 'always' will always confirm before sending.\n ++- 'never' will never confirm before sending.\n + - 'cc' will confirm before sending when send-email has automatically\n +- added addresses from the patch to the Cc list\n ++ added addresses from the patch to the Cc list.\n + - 'compose' will confirm before sending the first message when using --compose.\n +-- 'auto' is equivalent to 'cc' + 'compose'\n ++- 'auto' is equivalent to 'cc' + 'compose'.\n + --\n + +\n + Default is the value of `sendemail.confirm` configuration value; if that\n +@@ Documentation/git-send-email.adoc: have been specified, in which case default to 'compose'.\n + \tWhen an argument may be understood either as a reference or as a file name,\n + \tchoose to understand it as a format-patch argument (`--format-patch`)\n + \tor as a file name (`--no-format-patch`). By default, when such a conflict\n +-\toccurs, git send-email will fail.\n ++\toccurs, `git send-email` will fail.\n + \n + --quiet::\n +-\tMake git-send-email less verbose. One line per email should be\n ++\tMake `git send-email` less verbose. One line per email should be\n + \tall that is output.\n + \n + --[no-]validate::\n +@@ Documentation/git-send-email.adoc: edit `~/.gitconfig` to specify your account settings:\n + ----\n + \n + If you have multi-factor authentication set up on your Gmail account, you can\n +-generate an app-specific password for use with 'git send-email'. Visit\n ++generate an app-specific password for use with `git send-email`. Visit\n + https://security.google.com/settings/security/apppasswords to create it.\n + \n + You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n +@@ Documentation/git-send-email.adoc: helpers.\n + \n + Note: the following core Perl modules that may be installed with your\n + distribution of Perl are required:\n +-MIME::Base64, MIME::QuotedPrint, Net::Domain and Net::SMTP.\n ++\n ++https://metacpan.org/pod/MIME::Base64[MIME::Base64],\n ++https://metacpan.org/pod/MIME::QuotedPrint[MIME::QuotedPrint],\n ++https://metacpan.org/pod/Net::Domain[Net::Domain] and\n ++https://metacpan.org/pod/Net::SMTP[Net::SMTP].\n ++\n + These additional Perl modules are also required:\n +-Authen::SASL and Mail::Address.\n ++\n ++https://metacpan.org/pod/Authen::SASL[Authen::SASL] and\n ++https://metacpan.org/pod/Mail::Address[Mail::Address].\n + \n + \n + SEE ALSO\n-: ---------- > 3: b9e41e2492 docs: remove credential helper links for emails from gitcredentials\n-: ---------- > 4: a6ad7ac810 docs: make the purpose of using app password for Gmail more clear in send-email\n-- \n2.49.0.windows.1\n\n"},{"id":"519165","messageId":"xmqqa56vl1uq.fsf@gitster.g","threadId":"63454","inReplyTo":"20250528070521.17379-3-gargaditya08@live.com","subject":"Re: [PATCH v5 2/4] docs: improve formatting in git-send-email documentation","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-05-29T18:15:57Z","receivedAt":"2025-05-29T18:16:00Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Aditya Garg writes:\n\n> The current documentation for git-send-email had an inconsistent use of\n> \"\", ``, and '' for quoting. This commit improves the formatting by\n> using the same style throughout the documentation.\n\nNice.\n\n> Also, at some places, minor grammatical errors were fixed, and some\n> non existent links were removed.\n>\n> Finally, the cpan links of necessary perl modules have been added to\n> make their installation easier.\n\nHmmm.\n\n> sendemail.multiEdit::\n> -\tIf true (default), a single editor instance will be spawned to edit\n> +\tIf `true` (default), a single editor instance will be spawned to edit\n> \tfiles you have to edit (patches when `--annotate` is used, and the\n> -\tsummary when `--compose` is used). If false, files will be edited one\n> +\tsummary when `--compose` is used). If `false`, files will be edited one\n> \tafter the other, spawning a new editor each time.\n\nLooks good. \"edit files you have to edit\" reads somewhat funny, but\nthe topic of this change is to correct mark-up, so it is the right\nthing to do to leave it as-is, at least in this step.\n\n> sendemail.confirm::\n> @@ -101,7 +101,7 @@ sendemail.signedOffCc (deprecated)::\n> \n> sendemail.smtpBatchSize::\n> \tNumber of messages to be sent per connection, after that a relogin\n> -\twill happen. If the value is 0 or undefined, send all messages in\n> +\twill happen. If the value is `0` or undefined, send all messages in\n\nDitto. \"or undefined\" will make readers wonder how they would\nspecify such a value (i.e. 'undef' in Perl) in their configuration\nfile, and may need rephrasing, but again not within the topic of\nthis step.\n\n> -When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n> -Subject, Reply-To, and In-Reply-To headers specified in the message. If\n> -the body of the message (what you type after the headers and a blank\n> -line) only contains blank (or Git: prefixed) lines, the summary won't be\n> +When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n> +'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n> +message. If the body of the message (what you type after the headers and a\n> +blank line) only contains blank (or Git: prefixed) lines, the summary won't be\n\nShouldn't 'Git:' in \"or Git: prefixed\" be marked-up somehow as well?\n\nAs these mail header names are all literal parts, shouldn't ehy be\nmarked up like `To`, `Cc`, etc.?\n\n> -\tby 'c_rehash', or a single file containing one or more PEM format\n> -\tcertificates concatenated together: see verify(1) -CAfile and\n> -\t-CApath for more information on these). Set it to an empty string\n> +\tby `c_rehash`, or a single file containing one or more PEM format\n> +\tcertificates concatenated together). Set it to an empty string\n\nWhat is this change about? grammatical errors? non existent links?\ncpan links? It does not look any of these.\n\n> @@ -298,18 +297,18 @@ must be used for each option.\n> \tconnection and authentication problems.\n> \n> --batch-size=::\n> -\tSome email servers (e.g. smtp.163.com) limit the number emails to be\n> +\tSome email servers (e.g. 'smtp.163.com') limit the number of emails to be\n> \tsent per session (connection) and this will lead to a failure when\n> \tsending many messages. With this option, send-email will disconnect after\n> -\tsending $ messages and wait for a few seconds (see --relogin-delay)\n> -\tand reconnect, to work around such a limit. You may want to\n> -\tuse some form of credential helper to avoid having to retype\n> -\tyour password every time this happens. Defaults to the\n> +\tsending `$` messages and wait for a few seconds\n> +\t(see `--relogin-delay`) and reconnect, to work around such a limit.\n> +\tYou may want to use some form of credential helper to avoid having to\n> +\tretype your password every time this happens. Defaults to the\n> \t`sendemail.smtpBatchSize` configuration variable.\n> \n> --relogin-delay=::\n> -\tWaiting $ seconds before reconnecting to SMTP server. Used together\n> -\twith --batch-size option. Defaults to the `sendemail.smtpReloginDelay`\n> +\tWaiting `$` seconds before reconnecting to SMTP server. Used together\n> +\twith `--batch-size` option. Defaults to the `sendemail.smtpReloginDelay`\n> \tconfiguration variable.\n\nTogether with the previous hunk, \"$\" before the placeholder looks\nincorrect, but it would be preferrable to leave it alone in order to\nkeep the patch focused on mark-up fixes alone.\n\nAs and are both placeholders, not something the users\nwould literally give, neither `` or `num` is appropriate\nmark-up for them, though. Probably \"__\" (without double quotes\naround it), if you look at Documentation/CodingGuidelines, I guess.\n\n> Automating\n> @@ -318,7 +317,7 @@ Automating\n> --no-to::\n> --no-cc::\n> --no-bcc::\n> -\tClears any list of \"To:\", \"Cc:\", \"Bcc:\" addresses previously\n> +\tClears any list of 'To:', 'Cc:', 'Bcc:' addresses previously\n> \tset via config.\n\nThe same comment about mail-headers being literal applies here.\n\nEven though the proposed log message talks about \"minor grammatical\nerrors\" and \"non existent links\", I didn't spot any changes about\nthem. It is very possible that they are buried in the mark-up\nfixes---it would make the patch much better to separate out such\nchanges and group the changes of the exact same kind into a single\npatch.\n\nI'll stop here for now; I may come back and continue from here\nlater.\n\nThanks.\n"},{"id":"519166","messageId":"xmqq5xhjl09q.fsf@gitster.g","threadId":"63454","inReplyTo":"20250528070521.17379-5-gargaditya08@live.com","subject":"Re: [PATCH v5 4/4] docs: make the purpose of using app password for Gmail more clear in send-email","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-05-29T18:50:09Z","receivedAt":"2025-05-29T18:50:13Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Aditya Garg writes:\n\n> The current example for Gmail suggests using app passwords for\n> send-email if user has multi-factor authentication set up for their\n> account. However, it does not clarify that the user cannot use their\n> normal password in case they do not have multi-factor authentication\n> enabled.\n\nCorrect, and the clarification looks good.\n\n\n> This commit clarifies that app passwords are required and suggests using\n> OAuth2 if the user does not want to enable multi-factor authentication.\n\nDubious. If the user does want to use 2FA (or already does use it),\nthere may be reasons why they still want to go the oauth route, no?\n\n> ---\n> Documentation/git-send-email.adoc | 3 +++\n> 1 file changed, 3 insertions(+)\n\nNot signed off.\n\n>\n> diff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\n> index aff0861d29..99c126cd5a 100644\n> --- a/Documentation/git-send-email.adoc\n> +++ b/Documentation/git-send-email.adoc\n> @@ -524,9 +524,12 @@ edit `~/.gitconfig` to specify your account settings:\n> \tsmtpServerPort = 587\n> ----\n> \n> +Gmail does not allow using your account password for `git send-email`.\n> If you have multi-factor authentication set up on your Gmail account, you can\n> generate an app-specific password for use with `git send-email`. Visit\n> https://security.google.com/settings/security/apppasswords to create it.\n> +If you do not want to enable multi-factor authentication, you can use OAuth2.0\n> +authentication as described below.\n\nHow about phrasing it more neutrally like ...\n\n \"Alternatively, instead of using app-specific password, you can use ...\"\n\nThe original somehow makes it sound like using 2FA + app_password is\nthe golden way, and short of that you could fall back to OAUTH, but\nthat is not the impression you would want to give to your readers, I\nthink.\n\n> You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n> `XOAUTH2` are common methods used for this type of authentication. Gmail\n\nWhether you take my suggestion or not, I think the first sentence\nhere is now redundant and can be safely removed.\n\n"},{"id":"519167","messageId":"PN3PR01MB9597008B30AB91C9539E7C8CB866A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"xmqqa56vl1uq.fsf@gitster.g","subject":"Re: [PATCH v5 2/4] docs: improve formatting in git-send-email documentation","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-29T19:04:54Z","receivedAt":"2025-05-29T19:05:00Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\n> On 29 May 2025, at 11:46 PM, Junio C Hamano wrote:\n> \n> Aditya Garg writes:\n> \n>> The current documentation for git-send-email had an inconsistent use of\n>> \"\", ``, and '' for quoting. This commit improves the formatting by\n>> using the same style throughout the documentation.\n> \n> Nice.\n> \n>> Also, at some places, minor grammatical errors were fixed, and some\n>> non existent links were removed.\n>> \n>> Finally, the cpan links of necessary perl modules have been added to\n>> make their installation easier.\n> \n> Hmmm.\n> \n>> sendemail.multiEdit::\n>> - If true (default), a single editor instance will be spawned to edit\n>> + If `true` (default), a single editor instance will be spawned to edit\n>> files you have to edit (patches when `--annotate` is used, and the\n>> - summary when `--compose` is used). If false, files will be edited one\n>> + summary when `--compose` is used). If `false`, files will be edited one\n>> after the other, spawning a new editor each time.\n> \n> Looks good. \"edit files you have to edit\" reads somewhat funny, but\n> the topic of this change is to correct mark-up, so it is the right\n> thing to do to leave it as-is, at least in this step.\n> \n>> sendemail.confirm::\n>> @@ -101,7 +101,7 @@ sendemail.signedOffCc (deprecated)::\n>> \n>> sendemail.smtpBatchSize::\n>> Number of messages to be sent per connection, after that a relogin\n>> - will happen. If the value is 0 or undefined, send all messages in\n>> + will happen. If the value is `0` or undefined, send all messages in\n> \n> Ditto. \"or undefined\" will make readers wonder how they would\n> specify such a value (i.e. 'undef' in Perl) in their configuration\n> file, and may need rephrasing, but again not within the topic of\n> this step.\n> \n>> -When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n>> -Subject, Reply-To, and In-Reply-To headers specified in the message. If\n>> -the body of the message (what you type after the headers and a blank\n>> -line) only contains blank (or Git: prefixed) lines, the summary won't be\n>> +When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n>> +'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n>> +message. If the body of the message (what you type after the headers and a\n>> +blank line) only contains blank (or Git: prefixed) lines, the summary won't be\n> \n> Shouldn't 'Git:' in \"or Git: prefixed\" be marked-up somehow as well?\n> \n> As these mail header names are all literal parts, shouldn't ehy be\n> marked up like `To`, `Cc`, etc.?\n\nI think its ok to let these remain in '', and deviate from the rules a bit.\nIf backticks are used, it will be a mess when rendered on the website.\n\n> \n>> - by 'c_rehash', or a single file containing one or more PEM format\n>> - certificates concatenated together: see verify(1) -CAfile and\n>> - -CApath for more information on these). Set it to an empty string\n>> + by `c_rehash`, or a single file containing one or more PEM format\n>> + certificates concatenated together). Set it to an empty string\n> \n> What is this change about? grammatical errors? non existent links?\n> cpan links? It does not look any of these.\n\nNon existing links. Checkout the website.\n\n> \n>> @@ -298,18 +297,18 @@ must be used for each option.\n>> connection and authentication problems.\n>> \n>> --batch-size=::\n>> - Some email servers (e.g. smtp.163.com) limit the number emails to be\n>> + Some email servers (e.g. 'smtp.163.com') limit the number of emails to be\n>> sent per session (connection) and this will lead to a failure when\n>> sending many messages. With this option, send-email will disconnect after\n>> - sending $ messages and wait for a few seconds (see --relogin-delay)\n>> - and reconnect, to work around such a limit. You may want to\n>> - use some form of credential helper to avoid having to retype\n>> - your password every time this happens. Defaults to the\n>> + sending `$` messages and wait for a few seconds\n>> + (see `--relogin-delay`) and reconnect, to work around such a limit.\n>> + You may want to use some form of credential helper to avoid having to\n>> + retype your password every time this happens. Defaults to the\n>> `sendemail.smtpBatchSize` configuration variable.\n>> \n>> --relogin-delay=::\n>> - Waiting $ seconds before reconnecting to SMTP server. Used together\n>> - with --batch-size option. Defaults to the `sendemail.smtpReloginDelay`\n>> + Waiting `$` seconds before reconnecting to SMTP server. Used together\n>> + with `--batch-size` option. Defaults to the `sendemail.smtpReloginDelay`\n>> configuration variable.\n> \n> Together with the previous hunk, \"$\" before the placeholder looks\n> incorrect, but it would be preferrable to leave it alone in order to\n> keep the patch focused on mark-up fixes alone.\n> \n> As and are both placeholders, not something the users\n> would literally give, neither `` or `num` is appropriate\n> mark-up for them, though. Probably \"__\" (without double quotes\n> around it), if you look at Documentation/CodingGuidelines, I guess.\n\nOk\n\n> \n>> Automating\n>> @@ -318,7 +317,7 @@ Automating\n>> --no-to::\n>> --no-cc::\n>> --no-bcc::\n>> - Clears any list of \"To:\", \"Cc:\", \"Bcc:\" addresses previously\n>> + Clears any list of 'To:', 'Cc:', 'Bcc:' addresses previously\n>> set via config.\n> \n> The same comment about mail-headers being literal applies here.\n> \n> Even though the proposed log message talks about \"minor grammatical\n> errors\" and \"non existent links\", I didn't spot any changes about\n> them. It is very possible that they are buried in the mark-up\n> fixes---it would make the patch much better to separate out such\n> changes and group the changes of the exact same kind into a single\n> patch.\n\nMinor grammatical errors were that of a missing full stop at the end of a line.\n\nMissing links, look above.\n> \n> I'll stop here for now; I may come back and continue from here\n> later.\n> \n> Thanks.\n"},{"id":"519168","messageId":"PN3PR01MB959790451CAA275910CFE8D9B866A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"xmqq5xhjl09q.fsf@gitster.g","subject":"Re: [PATCH v5 4/4] docs: make the purpose of using app password for Gmail more clear in send-email","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-29T19:06:04Z","receivedAt":"2025-05-29T19:06:09Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\n> On 30 May 2025, at 12:20 AM, Junio C Hamano wrote:\n> \n> Aditya Garg writes:\n> \n>> The current example for Gmail suggests using app passwords for\n>> send-email if user has multi-factor authentication set up for their\n>> account. However, it does not clarify that the user cannot use their\n>> normal password in case they do not have multi-factor authentication\n>> enabled.\n> \n> Correct, and the clarification looks good.\n> \n> \n>> This commit clarifies that app passwords are required and suggests using\n>> OAuth2 if the user does not want to enable multi-factor authentication.\n> \n> Dubious. If the user does want to use 2FA (or already does use it),\n> there may be reasons why they still want to go the oauth route, no?\n> \n>> ---\n>> Documentation/git-send-email.adoc | 3 +++\n>> 1 file changed, 3 insertions(+)\n> \n> Not signed off.\n\nOops.\n\n> \n>> \n>> diff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\n>> index aff0861d29..99c126cd5a 100644\n>> --- a/Documentation/git-send-email.adoc\n>> +++ b/Documentation/git-send-email.adoc\n>> @@ -524,9 +524,12 @@ edit `~/.gitconfig` to specify your account settings:\n>> smtpServerPort = 587\n>> ----\n>> \n>> +Gmail does not allow using your account password for `git send-email`.\n>> If you have multi-factor authentication set up on your Gmail account, you can\n>> generate an app-specific password for use with `git send-email`. Visit\n>> https://security.google.com/settings/security/apppasswords to create it.\n>> +If you do not want to enable multi-factor authentication, you can use OAuth2.0\n>> +authentication as described below.\n> \n> How about phrasing it more neutrally like ...\n> \n> \"Alternatively, instead of using app-specific password, you can use ...\"\n> \n> The original somehow makes it sound like using 2FA + app_password is\n> the golden way, and short of that you could fall back to OAUTH, but\n> that is not the impression you would want to give to your readers, I\n> think.\n> \n>> You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n>> `XOAUTH2` are common methods used for this type of authentication. Gmail\n> \n> Whether you take my suggestion or not, I think the first sentence\n> here is now redundant and can be safely removed.\n> \n\nI'll take your suggestion, and just reword this whole thing in a bit better way."},{"id":"519214","messageId":"20250530113627.8639-1-gargaditya08@live.com","threadId":"63454","inReplyTo":"PN3PR01MB95971131BD3CD89771F19E5DB896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"[PATCH v6 0/4] docs: update email credential helpers and improve formatting","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T11:37:07Z","receivedAt":"2025-05-30T11:37:12Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"Hi all,\n\nThis patch series included three patches:\n\n1. The first patch adds a link to the `git-credential-yahoo` helper for\n Yahoo accounts and links Google's `sendgmail` tool as an alternative\n method for sending emails through Gmail.\n\n2. The second patch improves the formatting of the `git-send-email`\n documentation, making it more readable and consistent.\n\n3. The third patch removed the email credential helper links from the\n `gitcredentials` page. The links are still available in the\n `git-send-email` documentation, which is the right place for them.\n\nDetailed explanation of the changes has been done in individual patch.\n\nv2: - Removed instructions for Yahoo SMTP server since I've realised that\n Yahoo *was* a popular email service. Also, the instructions were\n just making the docs more crowded. I've also added a link to\n Google's `sendgmail` tool in the first patch. The second patch has been\n added to address the issues that came up here:\n https://github.com/git/git-scm.com/pull/2005\n\nv3: - Added a patch to improve the formatting of the `git-send-email`\n documentation.\n\nv4: - Added cpan links of the perl modules requires for `git-send-email`\n to work.\n\nv5: - Added a patch to make the purpose of using app password for Gmail\n more clear in `send-email` documentation.\n\nv6: - Reword the documentation a bit more in last patch.\n - Markdown Git: -> 'Git:' in the second patch.\n - Restore the non-existent link (atleast what I believed that to be) in the\n second patch.\n - Remove the unnecessary use of $ with and placeholders in the\n second patch.\n - White at it, also prefer using the word \"mechanism\" over \"method\" for\n `OAUTHBEARER` and `XOAUTH2` in git-send-email docs since that is what\n official docs use. This changes has been done in the last patch.\n\n NOTE: I have not used `` for Headers in the second patch. I think its ok\n to deviate a bit from the rules and not be army men here. If I\n markdown them as code, the whole doc will be filled with codestyled\n blocks, and I think, these headers demand \"different treatement\"\n than rest other code and variables. Codeblocks everywhere are more\n of hurting the readability of the documentation than helping it.\n\nAditya Garg (4):\n docs: add credential helper for yahoo and link Google's sendgmail tool\n docs: improve formatting in git-send-email documentation\n docs: remove credential helper links for emails from gitcredentials\n docs: make the purpose of using app password for Gmail more clear in\n send-email\n\n Documentation/config/sendemail.adoc | 8 +-\n Documentation/git-send-email.adoc | 203 +++++++++++++++-------------\n Documentation/gitcredentials.adoc | 4 -\n 3 files changed, 114 insertions(+), 101 deletions(-)\n\nRange-diff against v5:\n-: ---------- > 1: 2c47cc5396 docs: add credential helper for yahoo and link Google's sendgmail tool\n1: bc1d0471ca ! 2: 20da5d6a58 docs: improve formatting in git-send-email documentation\n @@ Commit message\n \n The current documentation for git-send-email had an inconsistent use of\n \"\", ``, and '' for quoting. This commit improves the formatting by\n - using the same style throughout the documentation.\n -\n - Also, at some places, minor grammatical errors were fixed, and some\n - non existent links were removed.\n + using the same style throughout the documentation. Missing full stops\n + have also been added at some places.\n \n Finally, the cpan links of necessary perl modules have been added to\n make their installation easier.\n \n + While at it, the unecessary use of $ with and placeholders\n + has also been removed.\n +\n Signed-off-by: Aditya Garg \n \n ## Documentation/config/sendemail.adoc ##\n @@ Documentation/git-send-email.adoc: This option may be specified multiple times.\n +When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n +'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n +message. If the body of the message (what you type after the headers and a\n -+blank line) only contains blank (or Git: prefixed) lines, the summary won't be\n ++blank line) only contains blank (or 'Git:' prefixed) lines, the summary won't be\n sent, but the headers mentioned above will be used unless they are\n removed.\n +\n @@ Documentation/git-send-email.adoc: must be used for each option.\n \tPath to a store of trusted CA certificates for SMTP SSL/TLS\n \tcertificate validation (either a directory that has been processed\n -\tby 'c_rehash', or a single file containing one or more PEM format\n --\tcertificates concatenated together: see verify(1) -CAfile and\n --\t-CApath for more information on these). Set it to an empty string\n +\tby `c_rehash`, or a single file containing one or more PEM format\n -+\tcertificates concatenated together). Set it to an empty string\n + \tcertificates concatenated together: see verify(1) -CAfile and\n + \t-CApath for more information on these). Set it to an empty string\n \tto disable certificate verification. Defaults to the value of the\n - \t`sendemail.smtpSSLCertPath` configuration variable, if set, or the\n - \tbacking SSL library's compiled-in default otherwise (which should\n @@ Documentation/git-send-email.adoc: must be used for each option.\n \tconnection and authentication problems.\n \n @@ Documentation/git-send-email.adoc: must be used for each option.\n -\tand reconnect, to work around such a limit. You may want to\n -\tuse some form of credential helper to avoid having to retype\n -\tyour password every time this happens. Defaults to the\n -+\tsending `$` messages and wait for a few seconds\n ++\tsending __ messages and wait for a few seconds\n +\t(see `--relogin-delay`) and reconnect, to work around such a limit.\n +\tYou may want to use some form of credential helper to avoid having to\n +\tretype your password every time this happens. Defaults to the\n @@ Documentation/git-send-email.adoc: must be used for each option.\n --relogin-delay=::\n -\tWaiting $ seconds before reconnecting to SMTP server. Used together\n -\twith --batch-size option. Defaults to the `sendemail.smtpReloginDelay`\n -+\tWaiting `$` seconds before reconnecting to SMTP server. Used together\n ++\tWaiting __ seconds before reconnecting to SMTP server. Used together\n +\twith `--batch-size` option. Defaults to the `sendemail.smtpReloginDelay`\n \tconfiguration variable.\n \n2: b9e41e2492 = 3: a05958c7aa docs: remove credential helper links for emails from gitcredentials\n3: a6ad7ac810 ! 4: 0bf48ac27d docs: make the purpose of using app password for Gmail more clear in send-email\n @@ Commit message\n enabled. Most likely the example was written in the days when Google\n allowed using normal passwords without multi-factor authentication.\n \n - This commit clarifies that app passwords are required and suggests using\n - OAuth2 if the user does not want to enable multi-factor authentication.\n + Clarify that regular passwords do not work for Gmail and app-passwords\n + are the only way for basic authentication. Also encourage users to use\n + OAuth2 as a more secure alternative.\n +\n + While at it, also prefer using the word \"mechanism\" over \"method\" for\n + `OAUTHBEARER` and `XOAUTH2` since that is what official docs use.\n +\n + Signed-off-by: Aditya Garg \n \n ## Documentation/git-send-email.adoc ##\n @@ Documentation/git-send-email.adoc: edit `~/.gitconfig` to specify your account settings:\n \tsmtpServerPort = 587\n ----\n \n -+Gmail does not allow using your account password for `git send-email`.\n ++Gmail does not allow using your regular password for `git send-email`.\n If you have multi-factor authentication set up on your Gmail account, you can\n generate an app-specific password for use with `git send-email`. Visit\n https://security.google.com/settings/security/apppasswords to create it.\n -+If you do not want to enable multi-factor authentication, you can use OAuth2.0\n -+authentication as described below.\n \n - You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n - `XOAUTH2` are common methods used for this type of authentication. Gmail\n +-You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n +-`XOAUTH2` are common methods used for this type of authentication. Gmail\n +-supports both of them. As an example, if you want to use `OAUTHBEARER`, edit\n +-your `~/.gitconfig` file and add `smtpAuth = OAUTHBEARER` to your account\n +-settings:\n ++Alternatively, instead of using an app-specific password, you can use\n ++OAuth2.0 authentication with Gmail. OAuth2.0 is more secure than\n ++app-specific passwords, and works regardless of whether you have multi-factor\n ++authentication set up. `OAUTHBEARER` and `XOAUTH2` are common mechanisms used\n ++for this type of authentication. Gmail supports both of them. As an example,\n ++if you want to use `OAUTHBEARER`, edit your `~/.gitconfig` file and add\n ++`smtpAuth = OAUTHBEARER` to your account settings:\n + \n + ----\n + [sendemail]\n +@@ Documentation/git-send-email.adoc: settings:\n + \tsmtpAuth = OAUTHBEARER\n + ----\n + \n +-Alternatively, you can use a tool developed by Google known as\n ++Another alternative is using a tool developed by Google known as\n + https://github.com/google/gmail-oauth2-tools/tree/master/go/sendgmail[sendgmail]\n + to send emails using `git send-email`.\n + \n +@@ Documentation/git-send-email.adoc: Use Microsoft Outlook as the SMTP Server\n + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n + Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.\n + Therefore, OAuth2.0 authentication must be used for Outlook. Also, it only\n +-supports `XOAUTH2` authentication method.\n ++supports `XOAUTH2` authentication mechanism.\n + \n + Edit `~/.gitconfig` to specify your account settings for Outlook and use its\n + SMTP server with `git send-email`:\n-- \n2.49.0.638.g03d7d6a772\n\n"},{"id":"519215","messageId":"20250530113627.8639-2-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250530113627.8639-1-gargaditya08@live.com","subject":"[PATCH v6 1/4] docs: add credential helper for yahoo and link Google's sendgmail tool","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T11:37:09Z","receivedAt":"2025-05-30T11:37:15Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"This commit links `git-credential-yahoo` as a credential helper for\nYahoo accounts. Also, Google's `sendgmail` tool has been linked as an\nalternative method for sending emails through Gmail.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/git-send-email.adoc | 10 ++++++++--\n 1 file changed, 8 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 26fda63c2f..81f8cbc6f3 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -543,6 +543,10 @@ settings:\n \tsmtpAuth = OAUTHBEARER\n ----\n \n+Alternatively, you can use a tool developed by Google known as\n+https://github.com/google/gmail-oauth2-tools/tree/master/go/sendgmail[sendgmail]\n+to send emails using `git send-email`.\n+\n Use Microsoft Outlook as the SMTP Server\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.\n@@ -579,8 +583,7 @@ next time.\n \n If you are using OAuth2.0 authentication, you need to use an access token in\n place of a password when prompted. Various OAuth2.0 token generators are\n-available online. Community maintained credential helpers for Gmail and Outlook\n-are also available:\n+available online. Community maintained credential helpers are also available:\n \n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail]\n \t (cross platform, dedicated helper for authenticating Gmail accounts)\n@@ -588,6 +591,9 @@ are also available:\n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook]\n \t (cross platform, dedicated helper for authenticating Microsoft Outlook accounts)\n \n+\t- https://github.com/AdityaGarg8/git-credential-email[git-credential-yahoo]\n+\t (cross platform, dedicated helper for authenticating Yahoo accounts)\n+\n You can also see linkgit:gitcredentials[7] for more OAuth based authentication\n helpers.\n \n-- \n2.49.0.638.g03d7d6a772\n\n"},{"id":"519216","messageId":"20250530113627.8639-3-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250530113627.8639-1-gargaditya08@live.com","subject":"[PATCH v6 2/4] docs: improve formatting in git-send-email documentation","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T11:37:10Z","receivedAt":"2025-05-30T11:37:17Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"The current documentation for git-send-email had an inconsistent use of\n\"\", ``, and '' for quoting. This commit improves the formatting by\nusing the same style throughout the documentation. Missing full stops\nhave also been added at some places.\n\nFinally, the cpan links of necessary perl modules have been added to\nmake their installation easier.\n\nWhile at it, the unecessary use of $ with and placeholders\nhas also been removed.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/config/sendemail.adoc | 8 +-\n Documentation/git-send-email.adoc | 178 +++++++++++++++-------------\n 2 files changed, 97 insertions(+), 89 deletions(-)\n\ndiff --git a/Documentation/config/sendemail.adoc b/Documentation/config/sendemail.adoc\nindex 5ffcfc9f2a..0b1b2766f5 100644\n--- a/Documentation/config/sendemail.adoc\n+++ b/Documentation/config/sendemail.adoc\n@@ -19,9 +19,9 @@ sendemail..*::\n \t`sendemail.identity`.\n \n sendemail.multiEdit::\n-\tIf true (default), a single editor instance will be spawned to edit\n+\tIf `true` (default), a single editor instance will be spawned to edit\n \tfiles you have to edit (patches when `--annotate` is used, and the\n-\tsummary when `--compose` is used). If false, files will be edited one\n+\tsummary when `--compose` is used). If `false`, files will be edited one\n \tafter the other, spawning a new editor each time.\n \n sendemail.confirm::\n@@ -101,7 +101,7 @@ sendemail.signedOffCc (deprecated)::\n \n sendemail.smtpBatchSize::\n \tNumber of messages to be sent per connection, after that a relogin\n-\twill happen. If the value is 0 or undefined, send all messages in\n+\twill happen. If the value is `0` or undefined, send all messages in\n \tone connection.\n \tSee also the `--batch-size` option of linkgit:git-send-email[1].\n \n@@ -111,5 +111,5 @@ sendemail.smtpReloginDelay::\n \n sendemail.forbidSendmailVariables::\n \tTo avoid common misconfiguration mistakes, linkgit:git-send-email[1]\n-\twill abort with a warning if any configuration options for \"sendmail\"\n+\twill abort with a warning if any configuration options for `sendmail`\n \texist. Set this variable to bypass the check.\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 81f8cbc6f3..04e1c459b4 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -21,7 +21,7 @@ Takes the patches given on the command line and emails them out.\n Patches can be specified as files, directories (which will send all\n files in the directory), or directly as a revision list. In the\n last case, any format accepted by linkgit:git-format-patch[1] can\n-be passed to git send-email, as well as options understood by\n+be passed to `git send-email`, as well as options understood by\n linkgit:git-format-patch[1].\n \n The header of the email is configurable via command-line options. If not\n@@ -35,11 +35,11 @@ There are two formats accepted for patch files:\n This is what linkgit:git-format-patch[1] generates. Most headers and MIME\n formatting are ignored.\n \n-2. The original format used by Greg Kroah-Hartman's 'send_lots_of_email.pl'\n+2. The original format used by Greg Kroah-Hartman's `send_lots_of_email.pl`\n script\n +\n-This format expects the first line of the file to contain the \"Cc:\" value\n-and the \"Subject:\" of the message as the second line.\n+This format expects the first line of the file to contain the 'Cc:' value\n+and the 'Subject:' of the message as the second line.\n \n \n OPTIONS\n@@ -54,13 +54,13 @@ Composing\n \t`sendemail.multiEdit`.\n \n --bcc=
,...::\n-\tSpecify a \"Bcc:\" value for each email. Default is the value of\n+\tSpecify a 'Bcc:' value for each email. Default is the value of\n \t`sendemail.bcc`.\n +\n This option may be specified multiple times.\n \n --cc=
,...::\n-\tSpecify a starting \"Cc:\" value for each email.\n+\tSpecify a starting 'Cc:' value for each email.\n \tDefault is the value of `sendemail.cc`.\n +\n This option may be specified multiple times.\n@@ -69,14 +69,14 @@ This option may be specified multiple times.\n \tInvoke a text editor (see GIT_EDITOR in linkgit:git-var[1])\n \tto edit an introductory message for the patch series.\n +\n-When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n-Subject, Reply-To, and In-Reply-To headers specified in the message. If\n-the body of the message (what you type after the headers and a blank\n-line) only contains blank (or Git: prefixed) lines, the summary won't be\n+When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n+'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n+message. If the body of the message (what you type after the headers and a\n+blank line) only contains blank (or 'Git:' prefixed) lines, the summary won't be\n sent, but the headers mentioned above will be used unless they are\n removed.\n +\n-Missing From or In-Reply-To headers will be prompted for.\n+Missing 'From' or 'In-Reply-To' headers will be prompted for.\n +\n See the CONFIGURATION section for `sendemail.multiEdit`.\n \n@@ -85,13 +85,13 @@ See the CONFIGURATION section for `sendemail.multiEdit`.\n \tthe value of the `sendemail.from` configuration option is used. If\n \tneither the command-line option nor `sendemail.from` are set, then the\n \tuser will be prompted for the value. The default for the prompt will be\n-\tthe value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not\n-\tset, as returned by \"git var -l\".\n+\tthe value of `GIT_AUTHOR_IDENT`, or `GIT_COMMITTER_IDENT` if that is not\n+\tset, as returned by `git var -l`.\n \n --reply-to=
::\n \tSpecify the address where replies from recipients should go to.\n \tUse this if replies to messages should go to another address than what\n-\tis specified with the --from parameter.\n+\tis specified with the `--from` parameter.\n \n --in-reply-to=::\n \tMake the first mail (or all the mails with `--no-thread`) appear as a\n@@ -112,14 +112,14 @@ illustration below where `[PATCH v2 0/3]` is in reply to `[PATCH 0/2]`:\n [PATCH v2 2/3] New tests\n [PATCH v2 3/3] Implementation\n +\n-Only necessary if --compose is also set. If --compose\n+Only necessary if `--compose` is also set. If `--compose`\n is not set, this will be prompted for.\n \n --[no-]outlook-id-fix::\n \tMicrosoft Outlook SMTP servers discard the Message-ID sent via email and\n \tassign a new random Message-ID, thus breaking threads.\n +\n-With `--outlook-id-fix`, 'git send-email' uses a mechanism specific to\n+With `--outlook-id-fix`, `git send-email` uses a mechanism specific to\n Outlook servers to learn the Message-ID the server assigned to fix the\n threading. Use it only when you know that the server reports the\n rewritten Message-ID the same way as Outlook servers do.\n@@ -130,14 +130,14 @@ to 'smtp.office365.com' or 'smtp-mail.outlook.com'. Use\n \n --subject=::\n \tSpecify the initial subject of the email thread.\n-\tOnly necessary if --compose is also set. If --compose\n+\tOnly necessary if `--compose` is also set. If `--compose`\n \tis not set, this will be prompted for.\n \n --to=
,...::\n \tSpecify the primary recipient of the emails generated. Generally, this\n \twill be the upstream maintainer of the project involved. Default is the\n \tvalue of the `sendemail.to` configuration value; if that is unspecified,\n-\tand --to-cmd is not specified, this will be prompted for.\n+\tand `--to-cmd` is not specified, this will be prompted for.\n +\n This option may be specified multiple times.\n \n@@ -145,30 +145,30 @@ This option may be specified multiple times.\n \tWhen encountering a non-ASCII message or subject that does not\n \tdeclare its encoding, add headers/quoting to indicate it is\n \tencoded in . Default is the value of the\n-\t'sendemail.assume8bitEncoding'; if that is unspecified, this\n+\t`sendemail.assume8bitEncoding`; if that is unspecified, this\n \twill be prompted for if any non-ASCII files are encountered.\n +\n Note that no attempts whatsoever are made to validate the encoding.\n \n --compose-encoding=::\n \tSpecify encoding of compose message. Default is the value of the\n-\t'sendemail.composeEncoding'; if that is unspecified, UTF-8 is assumed.\n+\t`sendemail.composeEncoding`; if that is unspecified, UTF-8 is assumed.\n \n --transfer-encoding=(7bit|8bit|quoted-printable|base64|auto)::\n \tSpecify the transfer encoding to be used to send the message over SMTP.\n-\t7bit will fail upon encountering a non-ASCII message. quoted-printable\n+\t'7bit' will fail upon encountering a non-ASCII message. 'quoted-printable'\n \tcan be useful when the repository contains files that contain carriage\n-\treturns, but makes the raw patch email file (as saved from a MUA) much\n-\tharder to inspect manually. base64 is even more fool proof, but also\n-\teven more opaque. auto will use 8bit when possible, and quoted-printable\n-\totherwise.\n+\treturns, but makes the raw patch email file (as saved from an MUA) much\n+\tharder to inspect manually. 'base64' is even more fool proof, but also\n+\teven more opaque. 'auto' will use '8bit' when possible, and\n+\t'quoted-printable' otherwise.\n +\n Default is the value of the `sendemail.transferEncoding` configuration\n-value; if that is unspecified, default to `auto`.\n+value; if that is unspecified, default to 'auto'.\n \n --xmailer::\n --no-xmailer::\n-\tAdd (or prevent adding) the \"X-Mailer:\" header. By default,\n+\tAdd (or prevent adding) the 'X-Mailer:' header. By default,\n \tthe header is added, but it can be turned off by setting the\n \t`sendemail.xmailer` configuration variable to `false`.\n \n@@ -179,8 +179,8 @@ Sending\n \tSpecify the envelope sender used to send the emails.\n \tThis is useful if your default address is not the address that is\n \tsubscribed to a list. In order to use the 'From' address, set the\n-\tvalue to \"auto\". If you use the sendmail binary, you must have\n-\tsuitable privileges for the -f parameter. Default is the value of the\n+\tvalue to `auto`. If you use the `sendmail` binary, you must have\n+\tsuitable privileges for the `-f` parameter. Default is the value of the\n \t`sendemail.envelopeSender` configuration variable; if that is\n \tunspecified, choosing the envelope sender is left to your MTA.\n \n@@ -189,8 +189,8 @@ Sending\n \tbe sendmail-like; specifically, it must support the `-i` option.\n \tThe command will be executed in the shell if necessary. Default\n \tis the value of `sendemail.sendmailCmd`. If unspecified, and if\n-\t--smtp-server is also unspecified, git-send-email will search\n-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH.\n+\t`--smtp-server` is also unspecified, `git send-email` will search\n+\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH`.\n \n --smtp-encryption=::\n \tSpecify in what way encrypting begins for the SMTP connection.\n@@ -209,7 +209,7 @@ Sending\n --smtp-domain=::\n \tSpecifies the Fully Qualified Domain Name (FQDN) used in the\n \tHELO/EHLO command to the SMTP server. Some servers require the\n-\tFQDN to match your IP address. If not set, git send-email attempts\n+\tFQDN to match your IP address. If not set, `git send-email` attempts\n \tto determine your FQDN automatically. Default is the value of\n \t`sendemail.smtpDomain`.\n \n@@ -223,10 +223,10 @@ $ git send-email --smtp-auth=\"PLAIN LOGIN GSSAPI\" ...\n +\n If at least one of the specified mechanisms matches the ones advertised by the\n SMTP server and if it is supported by the utilized SASL library, the mechanism\n-is used for authentication. If neither 'sendemail.smtpAuth' nor `--smtp-auth`\n+is used for authentication. If neither `sendemail.smtpAuth` nor `--smtp-auth`\n is specified, all mechanisms supported by the SASL library can be used. The\n-special value 'none' maybe specified to completely disable authentication\n-independently of `--smtp-user`\n+special value `none` maybe specified to completely disable authentication\n+independently of `--smtp-user`.\n \n --smtp-pass[=]::\n \tPassword for SMTP-AUTH. The argument is optional: If no\n@@ -238,16 +238,16 @@ Furthermore, passwords need not be specified in configuration files\n or on the command line. If a username has been specified (with\n `--smtp-user` or a `sendemail.smtpUser`), but no password has been\n specified (with `--smtp-pass` or `sendemail.smtpPass`), then\n-a password is obtained using 'git-credential'.\n+a password is obtained using linkgit:git-credential[1].\n \n --no-smtp-auth::\n-\tDisable SMTP authentication. Short hand for `--smtp-auth=none`\n+\tDisable SMTP authentication. Short hand for `--smtp-auth=none`.\n \n --smtp-server=::\n \tIf set, specifies the outgoing SMTP server to use (e.g.\n \t`smtp.example.com` or a raw IP address). If unspecified, and if\n \t`--sendmail-cmd` is also unspecified, the default is to search\n-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH if such a\n+\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH` if such a\n \tprogram is available, falling back to `localhost` otherwise.\n +\n For backward compatibility, this option can also specify a full pathname\n@@ -260,7 +260,7 @@ instead.\n \tSpecifies a port different from the default port (SMTP\n \tservers typically listen to smtp port 25, but may also listen to\n \tsubmission port 587, or the common SSL smtp port 465);\n-\tsymbolic port names (e.g. \"submission\" instead of 587)\n+\tsymbolic port names (e.g. `submission` instead of 587)\n \tare also accepted. The port can also be set with the\n \t`sendemail.smtpServerPort` configuration variable.\n \n@@ -269,7 +269,7 @@ instead.\n \tDefault value can be specified by the `sendemail.smtpServerOption`\n \tconfiguration option.\n +\n-The --smtp-server-option option must be repeated for each option you want\n+The `--smtp-server-option` option must be repeated for each option you want\n to pass to the server. Likewise, different lines in the configuration files\n must be used for each option.\n \n@@ -279,7 +279,7 @@ must be used for each option.\n --smtp-ssl-cert-path::\n \tPath to a store of trusted CA certificates for SMTP SSL/TLS\n \tcertificate validation (either a directory that has been processed\n-\tby 'c_rehash', or a single file containing one or more PEM format\n+\tby `c_rehash`, or a single file containing one or more PEM format\n \tcertificates concatenated together: see verify(1) -CAfile and\n \t-CApath for more information on these). Set it to an empty string\n \tto disable certificate verification. Defaults to the value of the\n@@ -298,18 +298,18 @@ must be used for each option.\n \tconnection and authentication problems.\n \n --batch-size=::\n-\tSome email servers (e.g. smtp.163.com) limit the number emails to be\n+\tSome email servers (e.g. 'smtp.163.com') limit the number of emails to be\n \tsent per session (connection) and this will lead to a failure when\n \tsending many messages. With this option, send-email will disconnect after\n-\tsending $ messages and wait for a few seconds (see --relogin-delay)\n-\tand reconnect, to work around such a limit. You may want to\n-\tuse some form of credential helper to avoid having to retype\n-\tyour password every time this happens. Defaults to the\n+\tsending __ messages and wait for a few seconds\n+\t(see `--relogin-delay`) and reconnect, to work around such a limit.\n+\tYou may want to use some form of credential helper to avoid having to\n+\tretype your password every time this happens. Defaults to the\n \t`sendemail.smtpBatchSize` configuration variable.\n \n --relogin-delay=::\n-\tWaiting $ seconds before reconnecting to SMTP server. Used together\n-\twith --batch-size option. Defaults to the `sendemail.smtpReloginDelay`\n+\tWaiting __ seconds before reconnecting to SMTP server. Used together\n+\twith `--batch-size` option. Defaults to the `sendemail.smtpReloginDelay`\n \tconfiguration variable.\n \n Automating\n@@ -318,7 +318,7 @@ Automating\n --no-to::\n --no-cc::\n --no-bcc::\n-\tClears any list of \"To:\", \"Cc:\", \"Bcc:\" addresses previously\n+\tClears any list of 'To:', 'Cc:', 'Bcc:' addresses previously\n \tset via config.\n \n --no-identity::\n@@ -327,13 +327,13 @@ Automating\n \n --to-cmd=::\n \tSpecify a command to execute once per patch file which\n-\tshould generate patch file specific \"To:\" entries.\n+\tshould generate patch file specific 'To:' entries.\n \tOutput of this command must be single email address per line.\n-\tDefault is the value of 'sendemail.toCmd' configuration value.\n+\tDefault is the value of `sendemail.toCmd` configuration value.\n \n --cc-cmd=::\n \tSpecify a command to execute once per patch file which\n-\tshould generate patch file specific \"Cc:\" entries.\n+\tshould generate patch file specific 'Cc:' entries.\n \tOutput of this command must be single email address per line.\n \tDefault is the value of `sendemail.ccCmd` configuration value.\n \n@@ -341,7 +341,7 @@ Automating\n \tSpecify a command that is executed once per outgoing message\n \tand output RFC 2822 style header lines to be inserted into\n \tthem. When the `sendemail.headerCmd` configuration variable is\n-\tset, its value is always used. When --header-cmd is provided\n+\tset, its value is always used. When `--header-cmd` is provided\n \tat the command line, its value takes precedence over the\n \t`sendemail.headerCmd` configuration variable.\n \n@@ -350,7 +350,7 @@ Automating\n \n --[no-]chain-reply-to::\n \tIf this is set, each email will be sent as a reply to the previous\n-\temail sent. If disabled with \"--no-chain-reply-to\", all emails after\n+\temail sent. If disabled with `--no-chain-reply-to`, all emails after\n \tthe first will be sent as replies to the first email sent. When using\n \tthis, it is recommended that the first file given be an overview of the\n \tentire patch series. Disabled by default, but the `sendemail.chainReplyTo`\n@@ -363,21 +363,22 @@ Automating\n \tthe value of `sendemail.identity`.\n \n --[no-]signed-off-by-cc::\n-\tIf this is set, add emails found in the `Signed-off-by` trailer or Cc: lines to the\n-\tcc list. Default is the value of `sendemail.signedOffByCc` configuration\n-\tvalue; if that is unspecified, default to --signed-off-by-cc.\n+\tIf this is set, add emails found in the `Signed-off-by` trailer or 'Cc:'\n+\tlines to the cc list. Default is the value of `sendemail.signedOffByCc`\n+\tconfiguration value; if that is unspecified, default to\n+\t`--signed-off-by-cc`.\n \n --[no-]cc-cover::\n-\tIf this is set, emails found in Cc: headers in the first patch of\n+\tIf this is set, emails found in 'Cc:' headers in the first patch of\n \tthe series (typically the cover letter) are added to the cc list\n-\tfor each email set. Default is the value of 'sendemail.ccCover'\n-\tconfiguration value; if that is unspecified, default to --no-cc-cover.\n+\tfor each email set. Default is the value of `sendemail.ccCover`\n+\tconfiguration value; if that is unspecified, default to `--no-cc-cover`.\n \n --[no-]to-cover::\n-\tIf this is set, emails found in To: headers in the first patch of\n+\tIf this is set, emails found in 'To:' headers in the first patch of\n \tthe series (typically the cover letter) are added to the to list\n-\tfor each email set. Default is the value of 'sendemail.toCover'\n-\tconfiguration value; if that is unspecified, default to --no-to-cover.\n+\tfor each email set. Default is the value of `sendemail.toCover`\n+\tconfiguration value; if that is unspecified, default to `--no-to-cover`.\n \n --suppress-cc=::\n \tSpecify an additional category of recipients to suppress the\n@@ -401,36 +402,36 @@ Automating\n --\n +\n Default is the value of `sendemail.suppressCc` configuration value; if\n-that is unspecified, default to 'self' if --suppress-from is\n-specified, as well as 'body' if --no-signed-off-cc is specified.\n+that is unspecified, default to 'self' if `--suppress-from` is\n+specified, as well as 'body' if `--no-signed-off-cc` is specified.\n \n --[no-]suppress-from::\n-\tIf this is set, do not add the From: address to the cc: list.\n+\tIf this is set, do not add the 'From:' address to the 'Cc:' list.\n \tDefault is the value of `sendemail.suppressFrom` configuration\n-\tvalue; if that is unspecified, default to --no-suppress-from.\n+\tvalue; if that is unspecified, default to `--no-suppress-from`.\n \n --[no-]thread::\n-\tIf this is set, the In-Reply-To and References headers will be\n+\tIf this is set, the 'In-Reply-To' and 'References' headers will be\n \tadded to each email sent. Whether each mail refers to the\n-\tprevious email (`deep` threading per 'git format-patch'\n+\tprevious email (`deep` threading per `git format-patch`\n \twording) or to the first email (`shallow` threading) is\n-\tgoverned by \"--[no-]chain-reply-to\".\n+\tgoverned by `--[no-]chain-reply-to`.\n +\n-If disabled with \"--no-thread\", those headers will not be added\n-(unless specified with --in-reply-to). Default is the value of the\n+If disabled with `--no-thread`, those headers will not be added\n+(unless specified with `--in-reply-to`). Default is the value of the\n `sendemail.thread` configuration value; if that is unspecified,\n-default to --thread.\n+default to `--thread`.\n +\n It is up to the user to ensure that no In-Reply-To header already\n-exists when 'git send-email' is asked to add it (especially note that\n-'git format-patch' can be configured to do the threading itself).\n+exists when `git send-email` is asked to add it (especially note that\n+`git format-patch` can be configured to do the threading itself).\n Failure to do so may not produce the expected result in the\n recipient's MUA.\n \n --[no-]mailmap::\n \tUse the mailmap file (see linkgit:gitmailmap[5]) to map all\n \taddresses to their canonical real name and email address. Additional\n-\tmailmap data specific to git-send-email may be provided using the\n+\tmailmap data specific to `git send-email` may be provided using the\n \t`sendemail.mailmap.file` or `sendemail.mailmap.blob` configuration\n \tvalues. Defaults to `sendemail.mailmap`.\n \n@@ -441,12 +442,12 @@ Administering\n \tConfirm just before sending:\n +\n --\n-- 'always' will always confirm before sending\n-- 'never' will never confirm before sending\n+- 'always' will always confirm before sending.\n+- 'never' will never confirm before sending.\n - 'cc' will confirm before sending when send-email has automatically\n- added addresses from the patch to the Cc list\n+ added addresses from the patch to the Cc list.\n - 'compose' will confirm before sending the first message when using --compose.\n-- 'auto' is equivalent to 'cc' + 'compose'\n+- 'auto' is equivalent to 'cc' + 'compose'.\n --\n +\n Default is the value of `sendemail.confirm` configuration value; if that\n@@ -460,10 +461,10 @@ have been specified, in which case default to 'compose'.\n \tWhen an argument may be understood either as a reference or as a file name,\n \tchoose to understand it as a format-patch argument (`--format-patch`)\n \tor as a file name (`--no-format-patch`). By default, when such a conflict\n-\toccurs, git send-email will fail.\n+\toccurs, `git send-email` will fail.\n \n --quiet::\n-\tMake git-send-email less verbose. One line per email should be\n+\tMake `git send-email` less verbose. One line per email should be\n \tall that is output.\n \n --[no-]validate::\n@@ -525,7 +526,7 @@ edit `~/.gitconfig` to specify your account settings:\n ----\n \n If you have multi-factor authentication set up on your Gmail account, you can\n-generate an app-specific password for use with 'git send-email'. Visit\n+generate an app-specific password for use with `git send-email`. Visit\n https://security.google.com/settings/security/apppasswords to create it.\n \n You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n@@ -599,9 +600,16 @@ helpers.\n \n Note: the following core Perl modules that may be installed with your\n distribution of Perl are required:\n-MIME::Base64, MIME::QuotedPrint, Net::Domain and Net::SMTP.\n+\n+https://metacpan.org/pod/MIME::Base64[MIME::Base64],\n+https://metacpan.org/pod/MIME::QuotedPrint[MIME::QuotedPrint],\n+https://metacpan.org/pod/Net::Domain[Net::Domain] and\n+https://metacpan.org/pod/Net::SMTP[Net::SMTP].\n+\n These additional Perl modules are also required:\n-Authen::SASL and Mail::Address.\n+\n+https://metacpan.org/pod/Authen::SASL[Authen::SASL] and\n+https://metacpan.org/pod/Mail::Address[Mail::Address].\n \n \n SEE ALSO\n-- \n2.49.0.638.g03d7d6a772\n\n"},{"id":"519217","messageId":"20250530113627.8639-4-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250530113627.8639-1-gargaditya08@live.com","subject":"[PATCH v6 3/4] docs: remove credential helper links for emails from gitcredentials","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T11:37:12Z","receivedAt":"2025-05-30T11:37:20Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"In a recent attempt to add links of email helpers to git-scm.com [1], I\ncame to a conclusion that the links in the gitcredentials page are meant\nfor people needing credential helpers for cloning, fetching and pushing\nrepositories to remote hosts, and not sending emails. gitcredentials\ndocs don't even talk about send emails, thus confirming this view.\n\nSo, lets remove these links from the gitcredentials page. The links are\nstill available in the git-send-email documentation, which is the right\nplace for them.\n\n[1]: https://github.com/git/git-scm.com/pull/2005\n\nSigned-off-by: Aditya Garg \n---\n Documentation/gitcredentials.adoc | 4 ----\n 1 file changed, 4 deletions(-)\n\ndiff --git a/Documentation/gitcredentials.adoc b/Documentation/gitcredentials.adoc\nindex b49923db02..3337bb475d 100644\n--- a/Documentation/gitcredentials.adoc\n+++ b/Documentation/gitcredentials.adoc\n@@ -133,10 +133,6 @@ Popular helpers with OAuth support include:\n \n - https://github.com/hickford/git-credential-oauth[git-credential-oauth] (cross platform, included in many Linux distributions)\n \n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail] (cross platform, dedicated helper to authenticate Gmail accounts for linkgit:git-send-email[1])\n-\n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook] (cross platform, dedicated helper to authenticate Microsoft Outlook accounts for linkgit:git-send-email[1])\n-\n CREDENTIAL CONTEXTS\n -------------------\n \n-- \n2.49.0.638.g03d7d6a772\n\n"},{"id":"519218","messageId":"20250530113627.8639-5-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250530113627.8639-1-gargaditya08@live.com","subject":"[PATCH v6 4/4] docs: make the purpose of using app password for Gmail more clear in send-email","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T11:37:14Z","receivedAt":"2025-05-30T11:37:22Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"The current example for Gmail suggests using app passwords for\nsend-email if user has multi-factor authentication set up for their\naccount. However, it does not clarify that the user cannot use their\nnormal password in case they do not have multi-factor authentication\nenabled. Most likely the example was written in the days when Google\nallowed using normal passwords without multi-factor authentication.\n\nClarify that regular passwords do not work for Gmail and app-passwords\nare the only way for basic authentication. Also encourage users to use\nOAuth2.0 as a more secure alternative.\n\nWhile at it, also prefer using the word \"mechanism\" over \"method\" for\n`OAUTHBEARER` and `XOAUTH2` since that is what official docs use.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/git-send-email.adoc | 17 ++++++++++-------\n 1 file changed, 10 insertions(+), 7 deletions(-)\n\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 04e1c459b4..9c008dabe3 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -525,15 +525,18 @@ edit `~/.gitconfig` to specify your account settings:\n \tsmtpServerPort = 587\n ----\n \n+Gmail does not allow using your regular password for `git send-email`.\n If you have multi-factor authentication set up on your Gmail account, you can\n generate an app-specific password for use with `git send-email`. Visit\n https://security.google.com/settings/security/apppasswords to create it.\n \n-You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n-`XOAUTH2` are common methods used for this type of authentication. Gmail\n-supports both of them. As an example, if you want to use `OAUTHBEARER`, edit\n-your `~/.gitconfig` file and add `smtpAuth = OAUTHBEARER` to your account\n-settings:\n+Alternatively, instead of using an app-specific password, you can use\n+OAuth2.0 authentication with Gmail. OAuth2.0 is more secure than\n+app-specific passwords, and works regardless of whether you have multi-factor\n+authentication set up. `OAUTHBEARER` and `XOAUTH2` are common mechanisms used\n+for this type of authentication. Gmail supports both of them. As an example,\n+if you want to use `OAUTHBEARER`, edit your `~/.gitconfig` file and add\n+`smtpAuth = OAUTHBEARER` to your account settings:\n \n ----\n [sendemail]\n@@ -544,7 +547,7 @@ settings:\n \tsmtpAuth = OAUTHBEARER\n ----\n \n-Alternatively, you can use a tool developed by Google known as\n+Another alternative is using a tool developed by Google known as\n https://github.com/google/gmail-oauth2-tools/tree/master/go/sendgmail[sendgmail]\n to send emails using `git send-email`.\n \n@@ -552,7 +555,7 @@ Use Microsoft Outlook as the SMTP Server\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.\n Therefore, OAuth2.0 authentication must be used for Outlook. Also, it only\n-supports `XOAUTH2` authentication method.\n+supports `XOAUTH2` authentication mechanism.\n \n Edit `~/.gitconfig` to specify your account settings for Outlook and use its\n SMTP server with `git send-email`:\n-- \n2.49.0.638.g03d7d6a772\n\n"},{"id":"519222","messageId":"877c1yb53w.fsf@gitster.g","threadId":"63454","inReplyTo":"PN3PR01MB9597008B30AB91C9539E7C8CB866A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"Re: [PATCH v5 2/4] docs: improve formatting in git-send-email documentation","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-05-30T13:28:03Z","receivedAt":"2025-05-30T13:28:12Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Aditya Garg writes:\n\n>>> -When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n>>> -Subject, Reply-To, and In-Reply-To headers specified in the message. If\n>>> -the body of the message (what you type after the headers and a blank\n>>> -line) only contains blank (or Git: prefixed) lines, the summary won't be\n>>> +When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n>>> +'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n>>> +message. If the body of the message (what you type after the headers and a\n>>> +blank line) only contains blank (or Git: prefixed) lines, the summary won't be\n>> \n>> Shouldn't 'Git:' in \"or Git: prefixed\" be marked-up somehow as well?\n>> \n>> As these mail header names are all literal parts, shouldn't ehy be\n>> marked up like `To`, `Cc`, etc.?\n>\n> I think its ok to let these remain in '', and deviate from the rules a bit.\n> If backticks are used, it will be a mess when rendered on the website.\n\nI do not think I agree; bending the rule only because the density of\nliterals in a single paragraph is too heavy does not sound like a\ngood application of a rule---it is hard to justify such an\nexception.\n\n>>> - by 'c_rehash', or a single file containing one or more PEM format\n>>> - certificates concatenated together: see verify(1) -CAfile and\n>>> - -CApath for more information on these). Set it to an empty string\n>>> + by `c_rehash`, or a single file containing one or more PEM format\n>>> + certificates concatenated together). Set it to an empty string\n>> \n>> What is this change about? grammatical errors? non existent links?\n>> cpan links? It does not look any of these.\n>\n> Non existing links. Checkout the website.\n\nBut I do not see any link in ...\n\n>>> - by 'c_rehash', or a single file containing one or more PEM format\n>>> - certificates concatenated together: see verify(1) -CAfile and\n>>> - -CApath for more information on these). Set it to an empty string\n\n... the text that was removed. The reference to verify(1) is a\ncommand in the OpenSSL suite, right?\n"},{"id":"519234","messageId":"PN3PR01MB9597DEE8C41CB1599B9A97CEB861A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"877c1yb53w.fsf@gitster.g","subject":"Re: [PATCH v5 2/4] docs: improve formatting in git-send-email documentation","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T13:32:14Z","receivedAt":"2025-05-30T13:32:19Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\n> On 30 May 2025, at 6:58 PM, Junio C Hamano wrote:\n> \n> Aditya Garg writes:\n> \n>>>> -When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n>>>> -Subject, Reply-To, and In-Reply-To headers specified in the message. If\n>>>> -the body of the message (what you type after the headers and a blank\n>>>> -line) only contains blank (or Git: prefixed) lines, the summary won't be\n>>>> +When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n>>>> +'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n>>>> +message. If the body of the message (what you type after the headers and a\n>>>> +blank line) only contains blank (or Git: prefixed) lines, the summary won't be\n>>> \n>>> Shouldn't 'Git:' in \"or Git: prefixed\" be marked-up somehow as well?\n>>> \n>>> As these mail header names are all literal parts, shouldn't ehy be\n>>> marked up like `To`, `Cc`, etc.?\n>> \n>> I think its ok to let these remain in '', and deviate from the rules a bit.\n>> If backticks are used, it will be a mess when rendered on the website.\n> \n> I do not think I agree; bending the rule only because the density of\n> literals in a single paragraph is too heavy does not sound like a\n> good application of a rule---it is hard to justify such an\n> exception.\n> \n>>>> - by 'c_rehash', or a single file containing one or more PEM format\n>>>> - certificates concatenated together: see verify(1) -CAfile and\n>>>> - -CApath for more information on these). Set it to an empty string\n>>>> + by `c_rehash`, or a single file containing one or more PEM format\n>>>> + certificates concatenated together). Set it to an empty string\n>>> \n>>> What is this change about? grammatical errors? non existent links?\n>>> cpan links? It does not look any of these.\n>> \n>> Non existing links. Checkout the website.\n> \n> But I do not see any link in ...\n> \n>>>> - by 'c_rehash', or a single file containing one or more PEM format\n>>>> - certificates concatenated together: see verify(1) -CAfile and\n>>>> - -CApath for more information on these). Set it to an empty string\n> \n> ... the text that was removed. The reference to verify(1) is a\n> command in the OpenSSL suite, right?\n\nIf this is a command, its not phrased nicely imo. I'll just leave it as is."},{"id":"519248","messageId":"C1E8439B-7666-472F-9C23-C558BA9ED53E@gmail.com","threadId":"63454","inReplyTo":"877c1yb53w.fsf@gitster.g","subject":"Re: [PATCH v5 2/4] docs: improve formatting in git-send-email documentation","fromName":"Ben Knoble","fromEmail":"ben.knoble@gmail.com","sentAt":"2025-05-30T14:48:28Z","receivedAt":"2025-05-30T14:48:41Z","isPatch":true,"sender":{"key":"ben.knoble@gmail.com","avatar":"https://avatars.githubusercontent.com/u/22802209?v=4"},"body":"\n> Le 30 mai 2025 à 09:28, Junio C Hamano a écrit :\n> \n> Aditya Garg writes:\n> \n>>>> -When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n>>>> -Subject, Reply-To, and In-Reply-To headers specified in the message. If\n>>>> -the body of the message (what you type after the headers and a blank\n>>>> -line) only contains blank (or Git: prefixed) lines, the summary won't be\n>>>> +When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n>>>> +'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n>>>> +message. If the body of the message (what you type after the headers and a\n>>>> +blank line) only contains blank (or Git: prefixed) lines, the summary won't be\n>>> \n>>> Shouldn't 'Git:' in \"or Git: prefixed\" be marked-up somehow as well?\n>>> \n>>> As these mail header names are all literal parts, shouldn't ehy be\n>>> marked up like `To`, `Cc`, etc.?\n>> \n>> I think its ok to let these remain in '', and deviate from the rules a bit.\n>> If backticks are used, it will be a mess when rendered on the website.\n> \n> I do not think I agree; bending the rule only because the density of\n> literals in a single paragraph is too heavy does not sound like a\n> good application of a rule---it is hard to justify such an\n> exception.\n\nTo go a bit further, rendered HTML is also not the only output format, though I don’t think the markup here affects manual pages substantially? So using « the website » (which? presumably git-scm.com) as justification prioritizes the look of one output format over other concerns, no?\n\nFor plaintext viewing, consistency is probably helpful. \n\n> \n>>>> - by 'c_rehash', or a single file containing one or more PEM format\n>>>> - certificates concatenated together: see verify(1) -CAfile and\n>>>> - -CApath for more information on these). Set it to an empty string\n>>>> + by `c_rehash`, or a single file containing one or more PEM format\n>>>> + certificates concatenated together). Set it to an empty string\n>>> \n>>> What is this change about? grammatical errors? non existent links?\n>>> cpan links? It does not look any of these.\n>> \n>> Non existing links. Checkout the website.\n> \n> But I do not see any link in ...\n> \n>>>> - by 'c_rehash', or a single file containing one or more PEM format\n>>>> - certificates concatenated together: see verify(1) -CAfile and\n>>>> - -CApath for more information on these). Set it to an empty string\n> \n> ... the text that was removed. The reference to verify(1) is a\n> command in the OpenSSL suite, right?\n> \n"},{"id":"519249","messageId":"PN3PR01MB95971B9CDF3DA9BDD9C5A0BEB861A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"C1E8439B-7666-472F-9C23-C558BA9ED53E@gmail.com","subject":"Re: [PATCH v5 2/4] docs: improve formatting in git-send-email documentation","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T14:51:45Z","receivedAt":"2025-05-30T14:51:50Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\n> On 30 May 2025, at 8:18 PM, Ben Knoble wrote:\n> \n> \n>> Le 30 mai 2025 à 09:28, Junio C Hamano a écrit :\n>> \n>> Aditya Garg writes:\n>> \n>>>>> -When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n>>>>> -Subject, Reply-To, and In-Reply-To headers specified in the message. If\n>>>>> -the body of the message (what you type after the headers and a blank\n>>>>> -line) only contains blank (or Git: prefixed) lines, the summary won't be\n>>>>> +When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n>>>>> +'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n>>>>> +message. If the body of the message (what you type after the headers and a\n>>>>> +blank line) only contains blank (or Git: prefixed) lines, the summary won't be\n>>>> \n>>>> Shouldn't 'Git:' in \"or Git: prefixed\" be marked-up somehow as well?\n>>>> \n>>>> As these mail header names are all literal parts, shouldn't ehy be\n>>>> marked up like `To`, `Cc`, etc.?\n>>> \n>>> I think its ok to let these remain in '', and deviate from the rules a bit.\n>>> If backticks are used, it will be a mess when rendered on the website.\n>> \n>> I do not think I agree; bending the rule only because the density of\n>> literals in a single paragraph is too heavy does not sound like a\n>> good application of a rule---it is hard to justify such an\n>> exception.\n> \n> To go a bit further, rendered HTML is also not the only output format, though I don’t think the markup here affects manual pages substantially? So using « the website » (which? presumably git-scm.com) as justification prioritizes the look of one output format over other concerns, no?\n> \n> For plaintext viewing, consistency is probably helpful. \n\nOk I'll send another revision."},{"id":"519265","messageId":"20250530154934.10077-1-gargaditya08@live.com","threadId":"63454","inReplyTo":"PN3PR01MB95971131BD3CD89771F19E5DB896A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"[PATCH v7 0/4] docs: add credential helper for yahoo and link Google's sendgmail tool","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T15:50:01Z","receivedAt":"2025-05-30T15:50:06Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"Hi all,\n\nThis patch series includes four patches:\n\n1. The first patch adds a link to the `git-credential-yahoo` helper for\n Yahoo accounts and links Google's `sendgmail` tool as an alternative\n method for sending emails through Gmail.\n\n2. The second patch improves the formatting of the `git-send-email`\n documentation, making it more readable and consistent.\n\n3. The third patch removes the email credential helper links from the\n `gitcredentials` page. The links are still available in the\n `git-send-email` documentation, which is the right place for them.\n\n4. The fourth patch clarifies the purpose of using an app password for\n Gmail in the `git-send-email` documentation. It also encourages\n users to use OAuth2.0 over app passwords for better security.\n\nDetailed explanation of the changes has been done in individual patch.\n\nv2: - Removed instructions for Yahoo SMTP server since I've realised that\n Yahoo *was* a popular email service. Also, the instructions were\n just making the docs more crowded. I've also added a link to\n Google's `sendgmail` tool in the first patch. The second patch has been\n added to address the issues that came up here:\n https://github.com/git/git-scm.com/pull/2005\n\nv3: - Added a patch to improve the formatting of the `git-send-email`\n documentation.\n\nv4: - Added cpan links of the perl modules requires for `git-send-email`\n to work.\n\nv5: - Added a patch to make the purpose of using app password for Gmail\n more clear in `send-email` documentation.\n\nv6: - Reword the documentation a bit more in last patch.\n - Markdown Git: -> 'Git:' in the second patch.\n - Restore the non-existent link (atleast what I believed that to be) in the\n second patch.\n - Remove the unnecessary use of $ with and placeholders in the\n second patch.\n - White at it, also prefer using the word \"mechanism\" over \"method\" for\n `OAUTHBEARER` and `XOAUTH2` in git-send-email docs since that is what\n official docs use. This changes has been done in the last patch.\n - Sign-off the last patch.\n\nv7: - Use backticks consistently for all headers as well in second patch.\n\nAditya Garg (4):\n docs: add credential helper for yahoo and link Google's sendgmail tool\n docs: improve formatting in git-send-email documentation\n docs: remove credential helper links for emails from gitcredentials\n docs: make the purpose of using app password for Gmail more clear in\n send-email\n\n Documentation/config/sendemail.adoc | 20 +--\n Documentation/git-send-email.adoc | 257 +++++++++++++++-------------\n Documentation/gitcredentials.adoc | 4 -\n 3 files changed, 147 insertions(+), 134 deletions(-)\n\nRange-diff against v6:\n-: ---------- > 1: 2c47cc5396 docs: add credential helper for yahoo and link Google's sendgmail tool\n1: 20da5d6a58 ! 2: 660305721d docs: improve formatting in git-send-email documentation\n @@ Commit message\n Signed-off-by: Aditya Garg \n \n ## Documentation/config/sendemail.adoc ##\n -@@ Documentation/config/sendemail.adoc: sendemail..*::\n +@@\n + sendemail.identity::\n + \tA configuration identity. When given, causes values in the\n +-\t'sendemail.' subsection to take precedence over\n +-\tvalues in the 'sendemail' section. The default identity is\n ++\t`sendemail.` subsection to take precedence over\n ++\tvalues in the `sendemail` section. The default identity is\n + \tthe value of `sendemail.identity`.\n + \n + sendemail.smtpEncryption::\n + \tSee linkgit:git-send-email[1] for description. Note that this\n +-\tsetting is not subject to the 'identity' mechanism.\n ++\tsetting is not subject to the `identity` mechanism.\n + \n + sendemail.smtpSSLCertPath::\n + \tPath to ca-certificates (either a directory or a single file).\n + \tSet it to an empty string to disable certificate verification.\n + \n + sendemail..*::\n +-\tIdentity-specific versions of the 'sendemail.*' parameters\n ++\tIdentity-specific versions of the `sendemail.*` parameters\n + \tfound below, taking precedence over those when this\n + \tidentity is selected, through either the command-line or\n \t`sendemail.identity`.\n \n sendemail.multiEdit::\n @@ Documentation/config/sendemail.adoc: sendemail..*::\n \tafter the other, spawning a new editor each time.\n \n sendemail.confirm::\n + \tSets the default for whether to confirm before sending. Must be\n +-\tone of 'always', 'never', 'cc', 'compose', or 'auto'. See `--confirm`\n ++\tone of `always`, `never`, `cc`, `compose`, or `auto`. See `--confirm`\n + \tin the linkgit:git-send-email[1] documentation for the meaning of these\n + \tvalues.\n + \n +@@ Documentation/config/sendemail.adoc: sendemail.aliasesFile::\n + \n + sendemail.aliasFileType::\n + \tFormat of the file(s) specified in sendemail.aliasesFile. Must be\n +-\tone of 'mutt', 'mailrc', 'pine', 'elm', 'gnus', or 'sendmail'.\n ++\tone of `mutt`, `mailrc`, `pine`, `elm`, `gnus`, or `sendmail`.\n + +\n + What an alias file in each format looks like can be found in\n + the documentation of the email program of the same name. The\n @@ Documentation/config/sendemail.adoc: sendemail.signedOffCc (deprecated)::\n \n sendemail.smtpBatchSize::\n @@ Documentation/git-send-email.adoc: There are two formats accepted for patch file\n +\n -This format expects the first line of the file to contain the \"Cc:\" value\n -and the \"Subject:\" of the message as the second line.\n -+This format expects the first line of the file to contain the 'Cc:' value\n -+and the 'Subject:' of the message as the second line.\n ++This format expects the first line of the file to contain the `Cc:` value\n ++and the `Subject:` of the message as the second line.\n \n \n OPTIONS\n @@ Documentation/git-send-email.adoc: Composing\n \n --bcc=
,...::\n -\tSpecify a \"Bcc:\" value for each email. Default is the value of\n -+\tSpecify a 'Bcc:' value for each email. Default is the value of\n ++\tSpecify a `Bcc:` value for each email. Default is the value of\n \t`sendemail.bcc`.\n +\n This option may be specified multiple times.\n \n --cc=
,...::\n -\tSpecify a starting \"Cc:\" value for each email.\n -+\tSpecify a starting 'Cc:' value for each email.\n ++\tSpecify a starting `Cc:` value for each email.\n \tDefault is the value of `sendemail.cc`.\n +\n This option may be specified multiple times.\n @@ Documentation/git-send-email.adoc: This option may be specified multiple times.\n -Subject, Reply-To, and In-Reply-To headers specified in the message. If\n -the body of the message (what you type after the headers and a blank\n -line) only contains blank (or Git: prefixed) lines, the summary won't be\n -+When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',\n -+'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the\n ++When `--compose` is used, `git send-email` will use the `From`, `To`, `Cc`,\n ++`Bcc`, `Subject`, `Reply-To`, and `In-Reply-To` headers specified in the\n +message. If the body of the message (what you type after the headers and a\n -+blank line) only contains blank (or 'Git:' prefixed) lines, the summary won't be\n ++blank line) only contains blank (or `Git:` prefixed) lines, the summary won't be\n sent, but the headers mentioned above will be used unless they are\n removed.\n +\n -Missing From or In-Reply-To headers will be prompted for.\n -+Missing 'From' or 'In-Reply-To' headers will be prompted for.\n ++Missing `From` or `In-Reply-To` headers will be prompted for.\n +\n See the CONFIGURATION section for `sendemail.multiEdit`.\n \n @@ Documentation/git-send-email.adoc: This option may be specified multiple times.\n --transfer-encoding=(7bit|8bit|quoted-printable|base64|auto)::\n \tSpecify the transfer encoding to be used to send the message over SMTP.\n -\t7bit will fail upon encountering a non-ASCII message. quoted-printable\n -+\t'7bit' will fail upon encountering a non-ASCII message. 'quoted-printable'\n ++\t`7bit` will fail upon encountering a non-ASCII message. `quoted-printable`\n \tcan be useful when the repository contains files that contain carriage\n -\treturns, but makes the raw patch email file (as saved from a MUA) much\n -\tharder to inspect manually. base64 is even more fool proof, but also\n -\teven more opaque. auto will use 8bit when possible, and quoted-printable\n -\totherwise.\n +\treturns, but makes the raw patch email file (as saved from an MUA) much\n -+\tharder to inspect manually. 'base64' is even more fool proof, but also\n -+\teven more opaque. 'auto' will use '8bit' when possible, and\n -+\t'quoted-printable' otherwise.\n ++\tharder to inspect manually. `base64` is even more fool proof, but also\n ++\teven more opaque. `auto` will use `8bit` when possible, and\n ++\t`quoted-printable` otherwise.\n +\n Default is the value of the `sendemail.transferEncoding` configuration\n --value; if that is unspecified, default to `auto`.\n -+value; if that is unspecified, default to 'auto'.\n + value; if that is unspecified, default to `auto`.\n \n --xmailer::\n --no-xmailer::\n -\tAdd (or prevent adding) the \"X-Mailer:\" header. By default,\n -+\tAdd (or prevent adding) the 'X-Mailer:' header. By default,\n ++\tAdd (or prevent adding) the `X-Mailer:` header. By default,\n \tthe header is added, but it can be turned off by setting the\n \t`sendemail.xmailer` configuration variable to `false`.\n \n @@ Documentation/git-send-email.adoc: Sending\n + --envelope-sender=
::\n \tSpecify the envelope sender used to send the emails.\n \tThis is useful if your default address is not the address that is\n - \tsubscribed to a list. In order to use the 'From' address, set the\n +-\tsubscribed to a list. In order to use the 'From' address, set the\n -\tvalue to \"auto\". If you use the sendmail binary, you must have\n -\tsuitable privileges for the -f parameter. Default is the value of the\n ++\tsubscribed to a list. In order to use the `From` address, set the\n +\tvalue to `auto`. If you use the `sendmail` binary, you must have\n +\tsuitable privileges for the `-f` parameter. Default is the value of the\n \t`sendemail.envelopeSender` configuration variable; if that is\n @@ Documentation/git-send-email.adoc: Sending\n \n --smtp-encryption=::\n \tSpecify in what way encrypting begins for the SMTP connection.\n -@@ Documentation/git-send-email.adoc: Sending\n +-\tValid values are 'ssl' and 'tls'. Any other value reverts to plain\n ++\tValid values are `ssl` and `tls`. Any other value reverts to plain\n + \t(unencrypted) SMTP, which defaults to port 25.\n + \tDespite the names, both values will use the same newer version of TLS,\n +-\tbut for historic reasons have these names. 'ssl' refers to \"implicit\"\n ++\tbut for historic reasons have these names. `ssl` refers to \"implicit\"\n + \tencryption (sometimes called SMTPS), that uses port 465 by default.\n +-\t'tls' refers to \"explicit\" encryption (often known as STARTTLS),\n ++\t`tls` refers to \"explicit\" encryption (often known as STARTTLS),\n + \tthat uses port 25 by default. Other ports might be used by the SMTP\n + \tserver, which are not the default. Commonly found alternative port for\n +-\t'tls' and unencrypted is 587. You need to check your provider's\n ++\t`tls` and unencrypted is 587. You need to check your provider's\n + \tdocumentation or your server configuration to make sure\n + \tfor your own case. Default is the value of `sendemail.smtpEncryption`.\n + \n --smtp-domain=::\n \tSpecifies the Fully Qualified Domain Name (FQDN) used in the\n \tHELO/EHLO command to the SMTP server. Some servers require the\n @@ Documentation/git-send-email.adoc: instead.\n to pass to the server. Likewise, different lines in the configuration files\n must be used for each option.\n \n -@@ Documentation/git-send-email.adoc: must be used for each option.\n + --smtp-ssl::\n +-\tLegacy alias for '--smtp-encryption ssl'.\n ++\tLegacy alias for `--smtp-encryption ssl`.\n + \n --smtp-ssl-cert-path::\n \tPath to a store of trusted CA certificates for SMTP SSL/TLS\n \tcertificate validation (either a directory that has been processed\n @@ Documentation/git-send-email.adoc: Automating\n --no-cc::\n --no-bcc::\n -\tClears any list of \"To:\", \"Cc:\", \"Bcc:\" addresses previously\n -+\tClears any list of 'To:', 'Cc:', 'Bcc:' addresses previously\n ++\tClears any list of `To:`, `Cc:`, `Bcc:` addresses previously\n \tset via config.\n \n --no-identity::\n @@ Documentation/git-send-email.adoc: Automating\n --to-cmd=::\n \tSpecify a command to execute once per patch file which\n -\tshould generate patch file specific \"To:\" entries.\n -+\tshould generate patch file specific 'To:' entries.\n ++\tshould generate patch file specific `To:` entries.\n \tOutput of this command must be single email address per line.\n -\tDefault is the value of 'sendemail.toCmd' configuration value.\n +\tDefault is the value of `sendemail.toCmd` configuration value.\n @@ Documentation/git-send-email.adoc: Automating\n --cc-cmd=::\n \tSpecify a command to execute once per patch file which\n -\tshould generate patch file specific \"Cc:\" entries.\n -+\tshould generate patch file specific 'Cc:' entries.\n ++\tshould generate patch file specific `Cc:` entries.\n \tOutput of this command must be single email address per line.\n \tDefault is the value of `sendemail.ccCmd` configuration value.\n \n @@ Documentation/git-send-email.adoc: Automating\n \tthis, it is recommended that the first file given be an overview of the\n \tentire patch series. Disabled by default, but the `sendemail.chainReplyTo`\n @@ Documentation/git-send-email.adoc: Automating\n + \n + --identity=::\n + \tA configuration identity. When given, causes values in the\n +-\t'sendemail.' subsection to take precedence over\n +-\tvalues in the 'sendemail' section. The default identity is\n ++\t`sendemail.` subsection to take precedence over\n ++\tvalues in the `sendemail` section. The default identity is\n \tthe value of `sendemail.identity`.\n \n --[no-]signed-off-by-cc::\n -\tIf this is set, add emails found in the `Signed-off-by` trailer or Cc: lines to the\n -\tcc list. Default is the value of `sendemail.signedOffByCc` configuration\n -\tvalue; if that is unspecified, default to --signed-off-by-cc.\n -+\tIf this is set, add emails found in the `Signed-off-by` trailer or 'Cc:'\n ++\tIf this is set, add emails found in the `Signed-off-by` trailer or `Cc:`\n +\tlines to the cc list. Default is the value of `sendemail.signedOffByCc`\n +\tconfiguration value; if that is unspecified, default to\n +\t`--signed-off-by-cc`.\n \n --[no-]cc-cover::\n -\tIf this is set, emails found in Cc: headers in the first patch of\n -+\tIf this is set, emails found in 'Cc:' headers in the first patch of\n ++\tIf this is set, emails found in `Cc:` headers in the first patch of\n \tthe series (typically the cover letter) are added to the cc list\n -\tfor each email set. Default is the value of 'sendemail.ccCover'\n -\tconfiguration value; if that is unspecified, default to --no-cc-cover.\n @@ Documentation/git-send-email.adoc: Automating\n \n --[no-]to-cover::\n -\tIf this is set, emails found in To: headers in the first patch of\n -+\tIf this is set, emails found in 'To:' headers in the first patch of\n ++\tIf this is set, emails found in `To:` headers in the first patch of\n \tthe series (typically the cover letter) are added to the to list\n -\tfor each email set. Default is the value of 'sendemail.toCover'\n -\tconfiguration value; if that is unspecified, default to --no-to-cover.\n @@ Documentation/git-send-email.adoc: Automating\n \n --suppress-cc=::\n \tSpecify an additional category of recipients to suppress the\n -@@ Documentation/git-send-email.adoc: Automating\n + \tauto-cc of:\n + +\n + --\n +-- 'author' will avoid including the patch author.\n +-- 'self' will avoid including the sender.\n +-- 'cc' will avoid including anyone mentioned in Cc lines in the patch header\n +- except for self (use 'self' for that).\n +-- 'bodycc' will avoid including anyone mentioned in Cc lines in the\n +- patch body (commit message) except for self (use 'self' for that).\n +-- 'sob' will avoid including anyone mentioned in the Signed-off-by trailers except\n +- for self (use 'self' for that).\n +-- 'misc-by' will avoid including anyone mentioned in Acked-by,\n ++- `author` will avoid including the patch author.\n ++- `self` will avoid including the sender.\n ++- `cc` will avoid including anyone mentioned in Cc lines in the patch header\n ++ except for self (use `self` for that).\n ++- `bodycc` will avoid including anyone mentioned in Cc lines in the\n ++ patch body (commit message) except for self (use `self` for that).\n ++- `sob` will avoid including anyone mentioned in the Signed-off-by trailers except\n ++ for self (use `self` for that).\n ++- `misc-by` will avoid including anyone mentioned in Acked-by,\n + Reviewed-by, Tested-by and other \"-by\" lines in the patch body,\n +- except Signed-off-by (use 'sob' for that).\n +-- 'cccmd' will avoid running the --cc-cmd.\n +-- 'body' is equivalent to 'sob' + 'bodycc' + 'misc-by'.\n +-- 'all' will suppress all auto cc values.\n ++ except Signed-off-by (use `sob` for that).\n ++- `cccmd` will avoid running the --cc-cmd.\n ++- `body` is equivalent to `sob` + `bodycc` + `misc-by`.\n ++- `all` will suppress all auto cc values.\n --\n +\n Default is the value of `sendemail.suppressCc` configuration value; if\n -that is unspecified, default to 'self' if --suppress-from is\n -specified, as well as 'body' if --no-signed-off-cc is specified.\n -+that is unspecified, default to 'self' if `--suppress-from` is\n -+specified, as well as 'body' if `--no-signed-off-cc` is specified.\n ++that is unspecified, default to `self` if `--suppress-from` is\n ++specified, as well as `body` if `--no-signed-off-cc` is specified.\n \n --[no-]suppress-from::\n -\tIf this is set, do not add the From: address to the cc: list.\n -+\tIf this is set, do not add the 'From:' address to the 'Cc:' list.\n ++\tIf this is set, do not add the `From:` address to the `Cc:` list.\n \tDefault is the value of `sendemail.suppressFrom` configuration\n -\tvalue; if that is unspecified, default to --no-suppress-from.\n +\tvalue; if that is unspecified, default to `--no-suppress-from`.\n \n --[no-]thread::\n -\tIf this is set, the In-Reply-To and References headers will be\n -+\tIf this is set, the 'In-Reply-To' and 'References' headers will be\n ++\tIf this is set, the `In-Reply-To` and `References` headers will be\n \tadded to each email sent. Whether each mail refers to the\n -\tprevious email (`deep` threading per 'git format-patch'\n +\tprevious email (`deep` threading per `git format-patch`\n @@ Documentation/git-send-email.adoc: Administering\n --\n -- 'always' will always confirm before sending\n -- 'never' will never confirm before sending\n -+- 'always' will always confirm before sending.\n -+- 'never' will never confirm before sending.\n - - 'cc' will confirm before sending when send-email has automatically\n +-- 'cc' will confirm before sending when send-email has automatically\n - added addresses from the patch to the Cc list\n -+ added addresses from the patch to the Cc list.\n - - 'compose' will confirm before sending the first message when using --compose.\n +-- 'compose' will confirm before sending the first message when using --compose.\n -- 'auto' is equivalent to 'cc' + 'compose'\n -+- 'auto' is equivalent to 'cc' + 'compose'.\n ++- `always` will always confirm before sending.\n ++- `never` will never confirm before sending.\n ++- `cc` will confirm before sending when send-email has automatically\n ++ added addresses from the patch to the Cc list.\n ++- `compose` will confirm before sending the first message when using --compose.\n ++- `auto` is equivalent to `cc` + `compose`.\n --\n +\n Default is the value of `sendemail.confirm` configuration value; if that\n +-is unspecified, default to 'auto' unless any of the suppress options\n +-have been specified, in which case default to 'compose'.\n ++is unspecified, default to `auto` unless any of the suppress options\n ++have been specified, in which case default to `compose`.\n + \n + --dry-run::\n + \tDo everything except actually send the emails.\n @@ Documentation/git-send-email.adoc: have been specified, in which case default to 'compose'.\n \tWhen an argument may be understood either as a reference or as a file name,\n \tchoose to understand it as a format-patch argument (`--format-patch`)\n @@ Documentation/git-send-email.adoc: have been specified, in which case default to\n \tall that is output.\n \n --[no-]validate::\n +@@ Documentation/git-send-email.adoc: have been specified, in which case default to 'compose'.\n + \t\t*\tInvoke the sendemail-validate hook if present (see linkgit:githooks[5]).\n + \t\t*\tWarn of patches that contain lines longer than\n + \t\t\t998 characters unless a suitable transfer encoding\n +-\t\t\t('auto', 'base64', or 'quoted-printable') is used;\n ++\t\t\t(`auto`, `base64`, or `quoted-printable`) is used;\n + \t\t\tthis is due to SMTP limits as described by\n + \t\t\thttps://www.ietf.org/rfc/rfc5322.txt.\n + --\n +@@ Documentation/git-send-email.adoc: Information\n + \tInstead of the normal operation, dump the shorthand alias names from\n + \tthe configured alias file(s), one per line in alphabetical order. Note\n + \tthat this only includes the alias name and not its expanded email addresses.\n +-\tSee 'sendemail.aliasesFile' for more information about aliases.\n ++\tSee `sendemail.aliasesFile` for more information about aliases.\n + \n + --translate-aliases::\n + \tInstead of the normal operation, read from standard input and\n + \tinterpret each line as an email alias. Translate it according to the\n + \tconfigured alias file(s). Output each translated name and email\n +-\taddress to standard output, one per line. See 'sendemail.aliasFile'\n ++\taddress to standard output, one per line. See `sendemail.aliasFile`\n + \tfor more information about aliases.\n + \n + CONFIGURATION\n @@ Documentation/git-send-email.adoc: edit `~/.gitconfig` to specify your account settings:\n ----\n \n2: a05958c7aa = 3: 4916bde9e5 docs: remove credential helper links for emails from gitcredentials\n3: e2dd5d9d81 = 4: 66c75485e2 docs: make the purpose of using app password for Gmail more clear in send-email\n-- \n2.49.0.639.ge2dd5d9d81\n\n"},{"id":"519266","messageId":"20250530154934.10077-2-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250530154934.10077-1-gargaditya08@live.com","subject":"[PATCH v7 1/4] docs: add credential helper for yahoo and link Google's sendgmail tool","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T15:50:02Z","receivedAt":"2025-05-30T15:50:09Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"This commit links `git-credential-yahoo` as a credential helper for\nYahoo accounts. Also, Google's `sendgmail` tool has been linked as an\nalternative method for sending emails through Gmail.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/git-send-email.adoc | 10 ++++++++--\n 1 file changed, 8 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 26fda63c2f..81f8cbc6f3 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -543,6 +543,10 @@ settings:\n \tsmtpAuth = OAUTHBEARER\n ----\n \n+Alternatively, you can use a tool developed by Google known as\n+https://github.com/google/gmail-oauth2-tools/tree/master/go/sendgmail[sendgmail]\n+to send emails using `git send-email`.\n+\n Use Microsoft Outlook as the SMTP Server\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.\n@@ -579,8 +583,7 @@ next time.\n \n If you are using OAuth2.0 authentication, you need to use an access token in\n place of a password when prompted. Various OAuth2.0 token generators are\n-available online. Community maintained credential helpers for Gmail and Outlook\n-are also available:\n+available online. Community maintained credential helpers are also available:\n \n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail]\n \t (cross platform, dedicated helper for authenticating Gmail accounts)\n@@ -588,6 +591,9 @@ are also available:\n \t- https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook]\n \t (cross platform, dedicated helper for authenticating Microsoft Outlook accounts)\n \n+\t- https://github.com/AdityaGarg8/git-credential-email[git-credential-yahoo]\n+\t (cross platform, dedicated helper for authenticating Yahoo accounts)\n+\n You can also see linkgit:gitcredentials[7] for more OAuth based authentication\n helpers.\n \n-- \n2.49.0.639.ge2dd5d9d81\n\n"},{"id":"519267","messageId":"20250530154934.10077-3-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250530154934.10077-1-gargaditya08@live.com","subject":"[PATCH v7 2/4] docs: improve formatting in git-send-email documentation","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T15:50:04Z","receivedAt":"2025-05-30T15:50:11Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"The current documentation for git-send-email had an inconsistent use of\n\"\", ``, and '' for quoting. This commit improves the formatting by\nusing the same style throughout the documentation. Missing full stops\nhave also been added at some places.\n\nFinally, the cpan links of necessary perl modules have been added to\nmake their installation easier.\n\nWhile at it, the unecessary use of $ with and placeholders\nhas also been removed.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/config/sendemail.adoc | 20 +--\n Documentation/git-send-email.adoc | 232 ++++++++++++++--------------\n 2 files changed, 130 insertions(+), 122 deletions(-)\n\ndiff --git a/Documentation/config/sendemail.adoc b/Documentation/config/sendemail.adoc\nindex 5ffcfc9f2a..54f1248e64 100644\n--- a/Documentation/config/sendemail.adoc\n+++ b/Documentation/config/sendemail.adoc\n@@ -1,32 +1,32 @@\n sendemail.identity::\n \tA configuration identity. When given, causes values in the\n-\t'sendemail.' subsection to take precedence over\n-\tvalues in the 'sendemail' section. The default identity is\n+\t`sendemail.` subsection to take precedence over\n+\tvalues in the `sendemail` section. The default identity is\n \tthe value of `sendemail.identity`.\n \n sendemail.smtpEncryption::\n \tSee linkgit:git-send-email[1] for description. Note that this\n-\tsetting is not subject to the 'identity' mechanism.\n+\tsetting is not subject to the `identity` mechanism.\n \n sendemail.smtpSSLCertPath::\n \tPath to ca-certificates (either a directory or a single file).\n \tSet it to an empty string to disable certificate verification.\n \n sendemail..*::\n-\tIdentity-specific versions of the 'sendemail.*' parameters\n+\tIdentity-specific versions of the `sendemail.*` parameters\n \tfound below, taking precedence over those when this\n \tidentity is selected, through either the command-line or\n \t`sendemail.identity`.\n \n sendemail.multiEdit::\n-\tIf true (default), a single editor instance will be spawned to edit\n+\tIf `true` (default), a single editor instance will be spawned to edit\n \tfiles you have to edit (patches when `--annotate` is used, and the\n-\tsummary when `--compose` is used). If false, files will be edited one\n+\tsummary when `--compose` is used). If `false`, files will be edited one\n \tafter the other, spawning a new editor each time.\n \n sendemail.confirm::\n \tSets the default for whether to confirm before sending. Must be\n-\tone of 'always', 'never', 'cc', 'compose', or 'auto'. See `--confirm`\n+\tone of `always`, `never`, `cc`, `compose`, or `auto`. See `--confirm`\n \tin the linkgit:git-send-email[1] documentation for the meaning of these\n \tvalues.\n \n@@ -51,7 +51,7 @@ sendemail.aliasesFile::\n \n sendemail.aliasFileType::\n \tFormat of the file(s) specified in sendemail.aliasesFile. Must be\n-\tone of 'mutt', 'mailrc', 'pine', 'elm', 'gnus', or 'sendmail'.\n+\tone of `mutt`, `mailrc`, `pine`, `elm`, `gnus`, or `sendmail`.\n +\n What an alias file in each format looks like can be found in\n the documentation of the email program of the same name. The\n@@ -101,7 +101,7 @@ sendemail.signedOffCc (deprecated)::\n \n sendemail.smtpBatchSize::\n \tNumber of messages to be sent per connection, after that a relogin\n-\twill happen. If the value is 0 or undefined, send all messages in\n+\twill happen. If the value is `0` or undefined, send all messages in\n \tone connection.\n \tSee also the `--batch-size` option of linkgit:git-send-email[1].\n \n@@ -111,5 +111,5 @@ sendemail.smtpReloginDelay::\n \n sendemail.forbidSendmailVariables::\n \tTo avoid common misconfiguration mistakes, linkgit:git-send-email[1]\n-\twill abort with a warning if any configuration options for \"sendmail\"\n+\twill abort with a warning if any configuration options for `sendmail`\n \texist. Set this variable to bypass the check.\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 81f8cbc6f3..5d13a856a7 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -21,7 +21,7 @@ Takes the patches given on the command line and emails them out.\n Patches can be specified as files, directories (which will send all\n files in the directory), or directly as a revision list. In the\n last case, any format accepted by linkgit:git-format-patch[1] can\n-be passed to git send-email, as well as options understood by\n+be passed to `git send-email`, as well as options understood by\n linkgit:git-format-patch[1].\n \n The header of the email is configurable via command-line options. If not\n@@ -35,11 +35,11 @@ There are two formats accepted for patch files:\n This is what linkgit:git-format-patch[1] generates. Most headers and MIME\n formatting are ignored.\n \n-2. The original format used by Greg Kroah-Hartman's 'send_lots_of_email.pl'\n+2. The original format used by Greg Kroah-Hartman's `send_lots_of_email.pl`\n script\n +\n-This format expects the first line of the file to contain the \"Cc:\" value\n-and the \"Subject:\" of the message as the second line.\n+This format expects the first line of the file to contain the `Cc:` value\n+and the `Subject:` of the message as the second line.\n \n \n OPTIONS\n@@ -54,13 +54,13 @@ Composing\n \t`sendemail.multiEdit`.\n \n --bcc=
,...::\n-\tSpecify a \"Bcc:\" value for each email. Default is the value of\n+\tSpecify a `Bcc:` value for each email. Default is the value of\n \t`sendemail.bcc`.\n +\n This option may be specified multiple times.\n \n --cc=
,...::\n-\tSpecify a starting \"Cc:\" value for each email.\n+\tSpecify a starting `Cc:` value for each email.\n \tDefault is the value of `sendemail.cc`.\n +\n This option may be specified multiple times.\n@@ -69,14 +69,14 @@ This option may be specified multiple times.\n \tInvoke a text editor (see GIT_EDITOR in linkgit:git-var[1])\n \tto edit an introductory message for the patch series.\n +\n-When `--compose` is used, git send-email will use the From, To, Cc, Bcc,\n-Subject, Reply-To, and In-Reply-To headers specified in the message. If\n-the body of the message (what you type after the headers and a blank\n-line) only contains blank (or Git: prefixed) lines, the summary won't be\n+When `--compose` is used, `git send-email` will use the `From`, `To`, `Cc`,\n+`Bcc`, `Subject`, `Reply-To`, and `In-Reply-To` headers specified in the\n+message. If the body of the message (what you type after the headers and a\n+blank line) only contains blank (or `Git:` prefixed) lines, the summary won't be\n sent, but the headers mentioned above will be used unless they are\n removed.\n +\n-Missing From or In-Reply-To headers will be prompted for.\n+Missing `From` or `In-Reply-To` headers will be prompted for.\n +\n See the CONFIGURATION section for `sendemail.multiEdit`.\n \n@@ -85,13 +85,13 @@ See the CONFIGURATION section for `sendemail.multiEdit`.\n \tthe value of the `sendemail.from` configuration option is used. If\n \tneither the command-line option nor `sendemail.from` are set, then the\n \tuser will be prompted for the value. The default for the prompt will be\n-\tthe value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not\n-\tset, as returned by \"git var -l\".\n+\tthe value of `GIT_AUTHOR_IDENT`, or `GIT_COMMITTER_IDENT` if that is not\n+\tset, as returned by `git var -l`.\n \n --reply-to=
::\n \tSpecify the address where replies from recipients should go to.\n \tUse this if replies to messages should go to another address than what\n-\tis specified with the --from parameter.\n+\tis specified with the `--from` parameter.\n \n --in-reply-to=::\n \tMake the first mail (or all the mails with `--no-thread`) appear as a\n@@ -112,14 +112,14 @@ illustration below where `[PATCH v2 0/3]` is in reply to `[PATCH 0/2]`:\n [PATCH v2 2/3] New tests\n [PATCH v2 3/3] Implementation\n +\n-Only necessary if --compose is also set. If --compose\n+Only necessary if `--compose` is also set. If `--compose`\n is not set, this will be prompted for.\n \n --[no-]outlook-id-fix::\n \tMicrosoft Outlook SMTP servers discard the Message-ID sent via email and\n \tassign a new random Message-ID, thus breaking threads.\n +\n-With `--outlook-id-fix`, 'git send-email' uses a mechanism specific to\n+With `--outlook-id-fix`, `git send-email` uses a mechanism specific to\n Outlook servers to learn the Message-ID the server assigned to fix the\n threading. Use it only when you know that the server reports the\n rewritten Message-ID the same way as Outlook servers do.\n@@ -130,14 +130,14 @@ to 'smtp.office365.com' or 'smtp-mail.outlook.com'. Use\n \n --subject=::\n \tSpecify the initial subject of the email thread.\n-\tOnly necessary if --compose is also set. If --compose\n+\tOnly necessary if `--compose` is also set. If `--compose`\n \tis not set, this will be prompted for.\n \n --to=
,...::\n \tSpecify the primary recipient of the emails generated. Generally, this\n \twill be the upstream maintainer of the project involved. Default is the\n \tvalue of the `sendemail.to` configuration value; if that is unspecified,\n-\tand --to-cmd is not specified, this will be prompted for.\n+\tand `--to-cmd` is not specified, this will be prompted for.\n +\n This option may be specified multiple times.\n \n@@ -145,30 +145,30 @@ This option may be specified multiple times.\n \tWhen encountering a non-ASCII message or subject that does not\n \tdeclare its encoding, add headers/quoting to indicate it is\n \tencoded in . Default is the value of the\n-\t'sendemail.assume8bitEncoding'; if that is unspecified, this\n+\t`sendemail.assume8bitEncoding`; if that is unspecified, this\n \twill be prompted for if any non-ASCII files are encountered.\n +\n Note that no attempts whatsoever are made to validate the encoding.\n \n --compose-encoding=::\n \tSpecify encoding of compose message. Default is the value of the\n-\t'sendemail.composeEncoding'; if that is unspecified, UTF-8 is assumed.\n+\t`sendemail.composeEncoding`; if that is unspecified, UTF-8 is assumed.\n \n --transfer-encoding=(7bit|8bit|quoted-printable|base64|auto)::\n \tSpecify the transfer encoding to be used to send the message over SMTP.\n-\t7bit will fail upon encountering a non-ASCII message. quoted-printable\n+\t`7bit` will fail upon encountering a non-ASCII message. `quoted-printable`\n \tcan be useful when the repository contains files that contain carriage\n-\treturns, but makes the raw patch email file (as saved from a MUA) much\n-\tharder to inspect manually. base64 is even more fool proof, but also\n-\teven more opaque. auto will use 8bit when possible, and quoted-printable\n-\totherwise.\n+\treturns, but makes the raw patch email file (as saved from an MUA) much\n+\tharder to inspect manually. `base64` is even more fool proof, but also\n+\teven more opaque. `auto` will use `8bit` when possible, and\n+\t`quoted-printable` otherwise.\n +\n Default is the value of the `sendemail.transferEncoding` configuration\n value; if that is unspecified, default to `auto`.\n \n --xmailer::\n --no-xmailer::\n-\tAdd (or prevent adding) the \"X-Mailer:\" header. By default,\n+\tAdd (or prevent adding) the `X-Mailer:` header. By default,\n \tthe header is added, but it can be turned off by setting the\n \t`sendemail.xmailer` configuration variable to `false`.\n \n@@ -178,9 +178,9 @@ Sending\n --envelope-sender=
::\n \tSpecify the envelope sender used to send the emails.\n \tThis is useful if your default address is not the address that is\n-\tsubscribed to a list. In order to use the 'From' address, set the\n-\tvalue to \"auto\". If you use the sendmail binary, you must have\n-\tsuitable privileges for the -f parameter. Default is the value of the\n+\tsubscribed to a list. In order to use the `From` address, set the\n+\tvalue to `auto`. If you use the `sendmail` binary, you must have\n+\tsuitable privileges for the `-f` parameter. Default is the value of the\n \t`sendemail.envelopeSender` configuration variable; if that is\n \tunspecified, choosing the envelope sender is left to your MTA.\n \n@@ -189,27 +189,27 @@ Sending\n \tbe sendmail-like; specifically, it must support the `-i` option.\n \tThe command will be executed in the shell if necessary. Default\n \tis the value of `sendemail.sendmailCmd`. If unspecified, and if\n-\t--smtp-server is also unspecified, git-send-email will search\n-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH.\n+\t`--smtp-server` is also unspecified, `git send-email` will search\n+\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH`.\n \n --smtp-encryption=::\n \tSpecify in what way encrypting begins for the SMTP connection.\n-\tValid values are 'ssl' and 'tls'. Any other value reverts to plain\n+\tValid values are `ssl` and `tls`. Any other value reverts to plain\n \t(unencrypted) SMTP, which defaults to port 25.\n \tDespite the names, both values will use the same newer version of TLS,\n-\tbut for historic reasons have these names. 'ssl' refers to \"implicit\"\n+\tbut for historic reasons have these names. `ssl` refers to \"implicit\"\n \tencryption (sometimes called SMTPS), that uses port 465 by default.\n-\t'tls' refers to \"explicit\" encryption (often known as STARTTLS),\n+\t`tls` refers to \"explicit\" encryption (often known as STARTTLS),\n \tthat uses port 25 by default. Other ports might be used by the SMTP\n \tserver, which are not the default. Commonly found alternative port for\n-\t'tls' and unencrypted is 587. You need to check your provider's\n+\t`tls` and unencrypted is 587. You need to check your provider's\n \tdocumentation or your server configuration to make sure\n \tfor your own case. Default is the value of `sendemail.smtpEncryption`.\n \n --smtp-domain=::\n \tSpecifies the Fully Qualified Domain Name (FQDN) used in the\n \tHELO/EHLO command to the SMTP server. Some servers require the\n-\tFQDN to match your IP address. If not set, git send-email attempts\n+\tFQDN to match your IP address. If not set, `git send-email` attempts\n \tto determine your FQDN automatically. Default is the value of\n \t`sendemail.smtpDomain`.\n \n@@ -223,10 +223,10 @@ $ git send-email --smtp-auth=\"PLAIN LOGIN GSSAPI\" ...\n +\n If at least one of the specified mechanisms matches the ones advertised by the\n SMTP server and if it is supported by the utilized SASL library, the mechanism\n-is used for authentication. If neither 'sendemail.smtpAuth' nor `--smtp-auth`\n+is used for authentication. If neither `sendemail.smtpAuth` nor `--smtp-auth`\n is specified, all mechanisms supported by the SASL library can be used. The\n-special value 'none' maybe specified to completely disable authentication\n-independently of `--smtp-user`\n+special value `none` maybe specified to completely disable authentication\n+independently of `--smtp-user`.\n \n --smtp-pass[=]::\n \tPassword for SMTP-AUTH. The argument is optional: If no\n@@ -238,16 +238,16 @@ Furthermore, passwords need not be specified in configuration files\n or on the command line. If a username has been specified (with\n `--smtp-user` or a `sendemail.smtpUser`), but no password has been\n specified (with `--smtp-pass` or `sendemail.smtpPass`), then\n-a password is obtained using 'git-credential'.\n+a password is obtained using linkgit:git-credential[1].\n \n --no-smtp-auth::\n-\tDisable SMTP authentication. Short hand for `--smtp-auth=none`\n+\tDisable SMTP authentication. Short hand for `--smtp-auth=none`.\n \n --smtp-server=::\n \tIf set, specifies the outgoing SMTP server to use (e.g.\n \t`smtp.example.com` or a raw IP address). If unspecified, and if\n \t`--sendmail-cmd` is also unspecified, the default is to search\n-\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH if such a\n+\tfor `sendmail` in `/usr/sbin`, `/usr/lib` and `$PATH` if such a\n \tprogram is available, falling back to `localhost` otherwise.\n +\n For backward compatibility, this option can also specify a full pathname\n@@ -260,7 +260,7 @@ instead.\n \tSpecifies a port different from the default port (SMTP\n \tservers typically listen to smtp port 25, but may also listen to\n \tsubmission port 587, or the common SSL smtp port 465);\n-\tsymbolic port names (e.g. \"submission\" instead of 587)\n+\tsymbolic port names (e.g. `submission` instead of 587)\n \tare also accepted. The port can also be set with the\n \t`sendemail.smtpServerPort` configuration variable.\n \n@@ -269,17 +269,17 @@ instead.\n \tDefault value can be specified by the `sendemail.smtpServerOption`\n \tconfiguration option.\n +\n-The --smtp-server-option option must be repeated for each option you want\n+The `--smtp-server-option` option must be repeated for each option you want\n to pass to the server. Likewise, different lines in the configuration files\n must be used for each option.\n \n --smtp-ssl::\n-\tLegacy alias for '--smtp-encryption ssl'.\n+\tLegacy alias for `--smtp-encryption ssl`.\n \n --smtp-ssl-cert-path::\n \tPath to a store of trusted CA certificates for SMTP SSL/TLS\n \tcertificate validation (either a directory that has been processed\n-\tby 'c_rehash', or a single file containing one or more PEM format\n+\tby `c_rehash`, or a single file containing one or more PEM format\n \tcertificates concatenated together: see verify(1) -CAfile and\n \t-CApath for more information on these). Set it to an empty string\n \tto disable certificate verification. Defaults to the value of the\n@@ -298,18 +298,18 @@ must be used for each option.\n \tconnection and authentication problems.\n \n --batch-size=::\n-\tSome email servers (e.g. smtp.163.com) limit the number emails to be\n+\tSome email servers (e.g. 'smtp.163.com') limit the number of emails to be\n \tsent per session (connection) and this will lead to a failure when\n \tsending many messages. With this option, send-email will disconnect after\n-\tsending $ messages and wait for a few seconds (see --relogin-delay)\n-\tand reconnect, to work around such a limit. You may want to\n-\tuse some form of credential helper to avoid having to retype\n-\tyour password every time this happens. Defaults to the\n+\tsending __ messages and wait for a few seconds\n+\t(see `--relogin-delay`) and reconnect, to work around such a limit.\n+\tYou may want to use some form of credential helper to avoid having to\n+\tretype your password every time this happens. Defaults to the\n \t`sendemail.smtpBatchSize` configuration variable.\n \n --relogin-delay=::\n-\tWaiting $ seconds before reconnecting to SMTP server. Used together\n-\twith --batch-size option. Defaults to the `sendemail.smtpReloginDelay`\n+\tWaiting __ seconds before reconnecting to SMTP server. Used together\n+\twith `--batch-size` option. Defaults to the `sendemail.smtpReloginDelay`\n \tconfiguration variable.\n \n Automating\n@@ -318,7 +318,7 @@ Automating\n --no-to::\n --no-cc::\n --no-bcc::\n-\tClears any list of \"To:\", \"Cc:\", \"Bcc:\" addresses previously\n+\tClears any list of `To:`, `Cc:`, `Bcc:` addresses previously\n \tset via config.\n \n --no-identity::\n@@ -327,13 +327,13 @@ Automating\n \n --to-cmd=::\n \tSpecify a command to execute once per patch file which\n-\tshould generate patch file specific \"To:\" entries.\n+\tshould generate patch file specific `To:` entries.\n \tOutput of this command must be single email address per line.\n-\tDefault is the value of 'sendemail.toCmd' configuration value.\n+\tDefault is the value of `sendemail.toCmd` configuration value.\n \n --cc-cmd=::\n \tSpecify a command to execute once per patch file which\n-\tshould generate patch file specific \"Cc:\" entries.\n+\tshould generate patch file specific `Cc:` entries.\n \tOutput of this command must be single email address per line.\n \tDefault is the value of `sendemail.ccCmd` configuration value.\n \n@@ -341,7 +341,7 @@ Automating\n \tSpecify a command that is executed once per outgoing message\n \tand output RFC 2822 style header lines to be inserted into\n \tthem. When the `sendemail.headerCmd` configuration variable is\n-\tset, its value is always used. When --header-cmd is provided\n+\tset, its value is always used. When `--header-cmd` is provided\n \tat the command line, its value takes precedence over the\n \t`sendemail.headerCmd` configuration variable.\n \n@@ -350,7 +350,7 @@ Automating\n \n --[no-]chain-reply-to::\n \tIf this is set, each email will be sent as a reply to the previous\n-\temail sent. If disabled with \"--no-chain-reply-to\", all emails after\n+\temail sent. If disabled with `--no-chain-reply-to`, all emails after\n \tthe first will be sent as replies to the first email sent. When using\n \tthis, it is recommended that the first file given be an overview of the\n \tentire patch series. Disabled by default, but the `sendemail.chainReplyTo`\n@@ -358,79 +358,80 @@ Automating\n \n --identity=::\n \tA configuration identity. When given, causes values in the\n-\t'sendemail.' subsection to take precedence over\n-\tvalues in the 'sendemail' section. The default identity is\n+\t`sendemail.` subsection to take precedence over\n+\tvalues in the `sendemail` section. The default identity is\n \tthe value of `sendemail.identity`.\n \n --[no-]signed-off-by-cc::\n-\tIf this is set, add emails found in the `Signed-off-by` trailer or Cc: lines to the\n-\tcc list. Default is the value of `sendemail.signedOffByCc` configuration\n-\tvalue; if that is unspecified, default to --signed-off-by-cc.\n+\tIf this is set, add emails found in the `Signed-off-by` trailer or `Cc:`\n+\tlines to the cc list. Default is the value of `sendemail.signedOffByCc`\n+\tconfiguration value; if that is unspecified, default to\n+\t`--signed-off-by-cc`.\n \n --[no-]cc-cover::\n-\tIf this is set, emails found in Cc: headers in the first patch of\n+\tIf this is set, emails found in `Cc:` headers in the first patch of\n \tthe series (typically the cover letter) are added to the cc list\n-\tfor each email set. Default is the value of 'sendemail.ccCover'\n-\tconfiguration value; if that is unspecified, default to --no-cc-cover.\n+\tfor each email set. Default is the value of `sendemail.ccCover`\n+\tconfiguration value; if that is unspecified, default to `--no-cc-cover`.\n \n --[no-]to-cover::\n-\tIf this is set, emails found in To: headers in the first patch of\n+\tIf this is set, emails found in `To:` headers in the first patch of\n \tthe series (typically the cover letter) are added to the to list\n-\tfor each email set. Default is the value of 'sendemail.toCover'\n-\tconfiguration value; if that is unspecified, default to --no-to-cover.\n+\tfor each email set. Default is the value of `sendemail.toCover`\n+\tconfiguration value; if that is unspecified, default to `--no-to-cover`.\n \n --suppress-cc=::\n \tSpecify an additional category of recipients to suppress the\n \tauto-cc of:\n +\n --\n-- 'author' will avoid including the patch author.\n-- 'self' will avoid including the sender.\n-- 'cc' will avoid including anyone mentioned in Cc lines in the patch header\n- except for self (use 'self' for that).\n-- 'bodycc' will avoid including anyone mentioned in Cc lines in the\n- patch body (commit message) except for self (use 'self' for that).\n-- 'sob' will avoid including anyone mentioned in the Signed-off-by trailers except\n- for self (use 'self' for that).\n-- 'misc-by' will avoid including anyone mentioned in Acked-by,\n+- `author` will avoid including the patch author.\n+- `self` will avoid including the sender.\n+- `cc` will avoid including anyone mentioned in Cc lines in the patch header\n+ except for self (use `self` for that).\n+- `bodycc` will avoid including anyone mentioned in Cc lines in the\n+ patch body (commit message) except for self (use `self` for that).\n+- `sob` will avoid including anyone mentioned in the Signed-off-by trailers except\n+ for self (use `self` for that).\n+- `misc-by` will avoid including anyone mentioned in Acked-by,\n Reviewed-by, Tested-by and other \"-by\" lines in the patch body,\n- except Signed-off-by (use 'sob' for that).\n-- 'cccmd' will avoid running the --cc-cmd.\n-- 'body' is equivalent to 'sob' + 'bodycc' + 'misc-by'.\n-- 'all' will suppress all auto cc values.\n+ except Signed-off-by (use `sob` for that).\n+- `cccmd` will avoid running the --cc-cmd.\n+- `body` is equivalent to `sob` + `bodycc` + `misc-by`.\n+- `all` will suppress all auto cc values.\n --\n +\n Default is the value of `sendemail.suppressCc` configuration value; if\n-that is unspecified, default to 'self' if --suppress-from is\n-specified, as well as 'body' if --no-signed-off-cc is specified.\n+that is unspecified, default to `self` if `--suppress-from` is\n+specified, as well as `body` if `--no-signed-off-cc` is specified.\n \n --[no-]suppress-from::\n-\tIf this is set, do not add the From: address to the cc: list.\n+\tIf this is set, do not add the `From:` address to the `Cc:` list.\n \tDefault is the value of `sendemail.suppressFrom` configuration\n-\tvalue; if that is unspecified, default to --no-suppress-from.\n+\tvalue; if that is unspecified, default to `--no-suppress-from`.\n \n --[no-]thread::\n-\tIf this is set, the In-Reply-To and References headers will be\n+\tIf this is set, the `In-Reply-To` and `References` headers will be\n \tadded to each email sent. Whether each mail refers to the\n-\tprevious email (`deep` threading per 'git format-patch'\n+\tprevious email (`deep` threading per `git format-patch`\n \twording) or to the first email (`shallow` threading) is\n-\tgoverned by \"--[no-]chain-reply-to\".\n+\tgoverned by `--[no-]chain-reply-to`.\n +\n-If disabled with \"--no-thread\", those headers will not be added\n-(unless specified with --in-reply-to). Default is the value of the\n+If disabled with `--no-thread`, those headers will not be added\n+(unless specified with `--in-reply-to`). Default is the value of the\n `sendemail.thread` configuration value; if that is unspecified,\n-default to --thread.\n+default to `--thread`.\n +\n It is up to the user to ensure that no In-Reply-To header already\n-exists when 'git send-email' is asked to add it (especially note that\n-'git format-patch' can be configured to do the threading itself).\n+exists when `git send-email` is asked to add it (especially note that\n+`git format-patch` can be configured to do the threading itself).\n Failure to do so may not produce the expected result in the\n recipient's MUA.\n \n --[no-]mailmap::\n \tUse the mailmap file (see linkgit:gitmailmap[5]) to map all\n \taddresses to their canonical real name and email address. Additional\n-\tmailmap data specific to git-send-email may be provided using the\n+\tmailmap data specific to `git send-email` may be provided using the\n \t`sendemail.mailmap.file` or `sendemail.mailmap.blob` configuration\n \tvalues. Defaults to `sendemail.mailmap`.\n \n@@ -441,17 +442,17 @@ Administering\n \tConfirm just before sending:\n +\n --\n-- 'always' will always confirm before sending\n-- 'never' will never confirm before sending\n-- 'cc' will confirm before sending when send-email has automatically\n- added addresses from the patch to the Cc list\n-- 'compose' will confirm before sending the first message when using --compose.\n-- 'auto' is equivalent to 'cc' + 'compose'\n+- `always` will always confirm before sending.\n+- `never` will never confirm before sending.\n+- `cc` will confirm before sending when send-email has automatically\n+ added addresses from the patch to the Cc list.\n+- `compose` will confirm before sending the first message when using --compose.\n+- `auto` is equivalent to `cc` + `compose`.\n --\n +\n Default is the value of `sendemail.confirm` configuration value; if that\n-is unspecified, default to 'auto' unless any of the suppress options\n-have been specified, in which case default to 'compose'.\n+is unspecified, default to `auto` unless any of the suppress options\n+have been specified, in which case default to `compose`.\n \n --dry-run::\n \tDo everything except actually send the emails.\n@@ -460,10 +461,10 @@ have been specified, in which case default to 'compose'.\n \tWhen an argument may be understood either as a reference or as a file name,\n \tchoose to understand it as a format-patch argument (`--format-patch`)\n \tor as a file name (`--no-format-patch`). By default, when such a conflict\n-\toccurs, git send-email will fail.\n+\toccurs, `git send-email` will fail.\n \n --quiet::\n-\tMake git-send-email less verbose. One line per email should be\n+\tMake `git send-email` less verbose. One line per email should be\n \tall that is output.\n \n --[no-]validate::\n@@ -474,7 +475,7 @@ have been specified, in which case default to 'compose'.\n \t\t*\tInvoke the sendemail-validate hook if present (see linkgit:githooks[5]).\n \t\t*\tWarn of patches that contain lines longer than\n \t\t\t998 characters unless a suitable transfer encoding\n-\t\t\t('auto', 'base64', or 'quoted-printable') is used;\n+\t\t\t(`auto`, `base64`, or `quoted-printable`) is used;\n \t\t\tthis is due to SMTP limits as described by\n \t\t\thttps://www.ietf.org/rfc/rfc5322.txt.\n --\n@@ -493,13 +494,13 @@ Information\n \tInstead of the normal operation, dump the shorthand alias names from\n \tthe configured alias file(s), one per line in alphabetical order. Note\n \tthat this only includes the alias name and not its expanded email addresses.\n-\tSee 'sendemail.aliasesFile' for more information about aliases.\n+\tSee `sendemail.aliasesFile` for more information about aliases.\n \n --translate-aliases::\n \tInstead of the normal operation, read from standard input and\n \tinterpret each line as an email alias. Translate it according to the\n \tconfigured alias file(s). Output each translated name and email\n-\taddress to standard output, one per line. See 'sendemail.aliasFile'\n+\taddress to standard output, one per line. See `sendemail.aliasFile`\n \tfor more information about aliases.\n \n CONFIGURATION\n@@ -525,7 +526,7 @@ edit `~/.gitconfig` to specify your account settings:\n ----\n \n If you have multi-factor authentication set up on your Gmail account, you can\n-generate an app-specific password for use with 'git send-email'. Visit\n+generate an app-specific password for use with `git send-email`. Visit\n https://security.google.com/settings/security/apppasswords to create it.\n \n You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n@@ -599,9 +600,16 @@ helpers.\n \n Note: the following core Perl modules that may be installed with your\n distribution of Perl are required:\n-MIME::Base64, MIME::QuotedPrint, Net::Domain and Net::SMTP.\n+\n+https://metacpan.org/pod/MIME::Base64[MIME::Base64],\n+https://metacpan.org/pod/MIME::QuotedPrint[MIME::QuotedPrint],\n+https://metacpan.org/pod/Net::Domain[Net::Domain] and\n+https://metacpan.org/pod/Net::SMTP[Net::SMTP].\n+\n These additional Perl modules are also required:\n-Authen::SASL and Mail::Address.\n+\n+https://metacpan.org/pod/Authen::SASL[Authen::SASL] and\n+https://metacpan.org/pod/Mail::Address[Mail::Address].\n \n \n SEE ALSO\n-- \n2.49.0.639.ge2dd5d9d81\n\n"},{"id":"519268","messageId":"20250530154934.10077-4-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250530154934.10077-1-gargaditya08@live.com","subject":"[PATCH v7 3/4] docs: remove credential helper links for emails from gitcredentials","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T15:50:05Z","receivedAt":"2025-05-30T15:50:15Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"In a recent attempt to add links of email helpers to git-scm.com [1], I\ncame to a conclusion that the links in the gitcredentials page are meant\nfor people needing credential helpers for cloning, fetching and pushing\nrepositories to remote hosts, and not sending emails. gitcredentials\ndocs don't even talk about send emails, thus confirming this view.\n\nSo, lets remove these links from the gitcredentials page. The links are\nstill available in the git-send-email documentation, which is the right\nplace for them.\n\n[1]: https://github.com/git/git-scm.com/pull/2005\n\nSigned-off-by: Aditya Garg \n---\n Documentation/gitcredentials.adoc | 4 ----\n 1 file changed, 4 deletions(-)\n\ndiff --git a/Documentation/gitcredentials.adoc b/Documentation/gitcredentials.adoc\nindex b49923db02..3337bb475d 100644\n--- a/Documentation/gitcredentials.adoc\n+++ b/Documentation/gitcredentials.adoc\n@@ -133,10 +133,6 @@ Popular helpers with OAuth support include:\n \n - https://github.com/hickford/git-credential-oauth[git-credential-oauth] (cross platform, included in many Linux distributions)\n \n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-gmail] (cross platform, dedicated helper to authenticate Gmail accounts for linkgit:git-send-email[1])\n-\n- - https://github.com/AdityaGarg8/git-credential-email[git-credential-outlook] (cross platform, dedicated helper to authenticate Microsoft Outlook accounts for linkgit:git-send-email[1])\n-\n CREDENTIAL CONTEXTS\n -------------------\n \n-- \n2.49.0.639.ge2dd5d9d81\n\n"},{"id":"519269","messageId":"20250530154934.10077-5-gargaditya08@live.com","threadId":"63454","inReplyTo":"20250530154934.10077-1-gargaditya08@live.com","subject":"[PATCH v7 4/4] docs: make the purpose of using app password for Gmail more clear in send-email","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T15:50:07Z","receivedAt":"2025-05-30T15:50:17Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"The current example for Gmail suggests using app passwords for\nsend-email if user has multi-factor authentication set up for their\naccount. However, it does not clarify that the user cannot use their\nnormal password in case they do not have multi-factor authentication\nenabled. Most likely the example was written in the days when Google\nallowed using normal passwords without multi-factor authentication.\n\nClarify that regular passwords do not work for Gmail and app-passwords\nare the only way for basic authentication. Also encourage users to use\nOAuth2.0 as a more secure alternative.\n\nWhile at it, also prefer using the word \"mechanism\" over \"method\" for\n`OAUTHBEARER` and `XOAUTH2` since that is what official docs use.\n\nSigned-off-by: Aditya Garg \n---\n Documentation/git-send-email.adoc | 17 ++++++++++-------\n 1 file changed, 10 insertions(+), 7 deletions(-)\n\ndiff --git a/Documentation/git-send-email.adoc b/Documentation/git-send-email.adoc\nindex 5d13a856a7..7bd09c254b 100644\n--- a/Documentation/git-send-email.adoc\n+++ b/Documentation/git-send-email.adoc\n@@ -525,15 +525,18 @@ edit `~/.gitconfig` to specify your account settings:\n \tsmtpServerPort = 587\n ----\n \n+Gmail does not allow using your regular password for `git send-email`.\n If you have multi-factor authentication set up on your Gmail account, you can\n generate an app-specific password for use with `git send-email`. Visit\n https://security.google.com/settings/security/apppasswords to create it.\n \n-You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n-`XOAUTH2` are common methods used for this type of authentication. Gmail\n-supports both of them. As an example, if you want to use `OAUTHBEARER`, edit\n-your `~/.gitconfig` file and add `smtpAuth = OAUTHBEARER` to your account\n-settings:\n+Alternatively, instead of using an app-specific password, you can use\n+OAuth2.0 authentication with Gmail. OAuth2.0 is more secure than\n+app-specific passwords, and works regardless of whether you have multi-factor\n+authentication set up. `OAUTHBEARER` and `XOAUTH2` are common mechanisms used\n+for this type of authentication. Gmail supports both of them. As an example,\n+if you want to use `OAUTHBEARER`, edit your `~/.gitconfig` file and add\n+`smtpAuth = OAUTHBEARER` to your account settings:\n \n ----\n [sendemail]\n@@ -544,7 +547,7 @@ settings:\n \tsmtpAuth = OAUTHBEARER\n ----\n \n-Alternatively, you can use a tool developed by Google known as\n+Another alternative is using a tool developed by Google known as\n https://github.com/google/gmail-oauth2-tools/tree/master/go/sendgmail[sendgmail]\n to send emails using `git send-email`.\n \n@@ -552,7 +555,7 @@ Use Microsoft Outlook as the SMTP Server\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n Unlike Gmail, Microsoft Outlook no longer supports app-specific passwords.\n Therefore, OAuth2.0 authentication must be used for Outlook. Also, it only\n-supports `XOAUTH2` authentication method.\n+supports `XOAUTH2` authentication mechanism.\n \n Edit `~/.gitconfig` to specify your account settings for Outlook and use its\n SMTP server with `git send-email`:\n-- \n2.49.0.639.ge2dd5d9d81\n\n"},{"id":"519272","messageId":"xmqqbjraf29c.fsf@gitster.g","threadId":"63454","inReplyTo":"PN3PR01MB9597DEE8C41CB1599B9A97CEB861A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"Re: [PATCH v5 2/4] docs: improve formatting in git-send-email documentation","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-05-30T17:15:59Z","receivedAt":"2025-05-30T17:16:02Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Aditya Garg writes:\n\n>> But I do not see any link in ...\n>> \n>>>>> - by 'c_rehash', or a single file containing one or more PEM format\n>>>>> - certificates concatenated together: see verify(1) -CAfile and\n>>>>> - -CApath for more information on these). Set it to an empty string\n>> \n>> ... the text that was removed. The reference to verify(1) is a\n>> command in the OpenSSL suite, right?\n>\n> If this is a command, its not phrased nicely imo. I'll just leave it as is.\n\nIn any case, there isn't an link in the document that is dangling,\nis there? It is not like I am trying to prove you wrong. I am\ntrying to see if the change you made is still addressing a valid\nconcern, and if so if there is a way to make the result better,\npossibly in some other ways.\n\nI agree with you that this passage is not nice to expect that the\nreaders are familiar with what appears in\n\n https://docs.openssl.org/master/man1/openssl-verify/\n\nwhere `-CAfile` and `-CApath` are two of the command line options\ndescribed there and has \"more information on these\". The\ndescription of these options on that page redirects us to\n\n https://docs.openssl.org/master/man1/openssl-verification-options/\n\nand expects us to scroll down to #trusted-certificate-options\nanchor, which is doubly unnice, but that part is not a fault of our\nown documentation ;-).\n\nPerhaps something like this would clarify the description?\n\n Documentation/git-send-email.adoc | 6 ++++--\n 1 file changed, 4 insertions(+), 2 deletions(-)\n\ndiff --git c/Documentation/git-send-email.adoc w/Documentation/git-send-email.adoc\nindex 7f223db42d..53f30fccf9 100644\n--- c/Documentation/git-send-email.adoc\n+++ w/Documentation/git-send-email.adoc\n@@ -267,8 +267,10 @@ must be used for each option.\n \tPath to a store of trusted CA certificates for SMTP SSL/TLS\n \tcertificate validation (either a directory that has been processed\n \tby 'c_rehash', or a single file containing one or more PEM format\n-\tcertificates concatenated together: see verify(1) -CAfile and\n-\t-CApath for more information on these). Set it to an empty string\n+\tcertificates concatenated together: see the description of the\n+\t`-CAfile` __ and the `-CApath` __ options of OpenSSL's\n+\t`verify(1)` manual page for more information on these).\n+\tSet it to an empty string\n \tto disable certificate verification. Defaults to the value of the\n \t`sendemail.smtpSSLCertPath` configuration variable, if set, or the\n \tbacking SSL library's compiled-in default otherwise (which should\n\n\n"},{"id":"519273","messageId":"PN3PR01MB95974BABA153882DE494D06EB861A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","threadId":"63454","inReplyTo":"xmqqbjraf29c.fsf@gitster.g","subject":"Re: [PATCH v5 2/4] docs: improve formatting in git-send-email documentation","fromName":"Aditya Garg","fromEmail":"gargaditya08@live.com","sentAt":"2025-05-30T17:19:21Z","receivedAt":"2025-05-30T17:19:29Z","isPatch":true,"sender":{"key":"gargaditya08@live.com","avatar":"https://avatars.githubusercontent.com/u/85610623?v=4"},"body":"\n\nOn 30/05/25 10:45 pm, Junio C Hamano wrote:\n> Aditya Garg writes:\n> \n>>> But I do not see any link in ...\n>>>\n>>>>>> - by 'c_rehash', or a single file containing one or more PEM format\n>>>>>> - certificates concatenated together: see verify(1) -CAfile and\n>>>>>> - -CApath for more information on these). Set it to an empty string\n>>>\n>>> ... the text that was removed. The reference to verify(1) is a\n>>> command in the OpenSSL suite, right?\n>>\n>> If this is a command, its not phrased nicely imo. I'll just leave it as is.\n> \n> In any case, there isn't an link in the document that is dangling,\n> is there? It is not like I am trying to prove you wrong. I am\n> trying to see if the change you made is still addressing a valid\n> concern, and if so if there is a way to make the result better,\n> possibly in some other ways.\n> \n> I agree with you that this passage is not nice to expect that the\n> readers are familiar with what appears in\n> \n> https://docs.openssl.org/master/man1/openssl-verify/\n> \n> where `-CAfile` and `-CApath` are two of the command line options\n> described there and has \"more information on these\". The\n> description of these options on that page redirects us to\n> \n> https://docs.openssl.org/master/man1/openssl-verification-options/\n> \n> and expects us to scroll down to #trusted-certificate-options\n> anchor, which is doubly unnice, but that part is not a fault of our\n> own documentation ;-).\n> \n> Perhaps something like this would clarify the description?\n\nThats definitely much better. Although, not really in the scope\nof this patch series ;)\n\nMaybe you could just append this alongwith v7 (the latest version\nof this patch series at the time of writing)?\n\n> \n> Documentation/git-send-email.adoc | 6 ++++--\n> 1 file changed, 4 insertions(+), 2 deletions(-)\n> \n> diff --git c/Documentation/git-send-email.adoc w/Documentation/git-send-email.adoc\n> index 7f223db42d..53f30fccf9 100644\n> --- c/Documentation/git-send-email.adoc\n> +++ w/Documentation/git-send-email.adoc\n> @@ -267,8 +267,10 @@ must be used for each option.\n> \tPath to a store of trusted CA certificates for SMTP SSL/TLS\n> \tcertificate validation (either a directory that has been processed\n> \tby 'c_rehash', or a single file containing one or more PEM format\n> -\tcertificates concatenated together: see verify(1) -CAfile and\n> -\t-CApath for more information on these). Set it to an empty string\n> +\tcertificates concatenated together: see the description of the\n> +\t`-CAfile` __ and the `-CApath` __ options of OpenSSL's\n> +\t`verify(1)` manual page for more information on these).\n> +\tSet it to an empty string\n> \tto disable certificate verification. Defaults to the value of the\n> \t`sendemail.smtpSSLCertPath` configuration variable, if set, or the\n> \tbacking SSL library's compiled-in default otherwise (which should\n> \n> \n\n"},{"id":"519274","messageId":"xmqq4ix2f1nx.fsf@gitster.g","threadId":"63454","inReplyTo":"20250530154934.10077-5-gargaditya08@live.com","subject":"Re: [PATCH v7 4/4] docs: make the purpose of using app password for Gmail more clear in send-email","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-05-30T17:28:50Z","receivedAt":"2025-05-30T17:28:54Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Aditya Garg writes:\n\n> +Gmail does not allow using your regular password for `git send-email`.\n> If you have multi-factor authentication set up on your Gmail account, you can\n> generate an app-specific password for use with `git send-email`. Visit\n> https://security.google.com/settings/security/apppasswords to create it.\n> \n> -You can also use OAuth2.0 authentication with Gmail. `OAUTHBEARER` and\n> -`XOAUTH2` are common methods used for this type of authentication. Gmail\n> -supports both of them. As an example, if you want to use `OAUTHBEARER`, edit\n> -your `~/.gitconfig` file and add `smtpAuth = OAUTHBEARER` to your account\n> -settings:\n> +Alternatively, instead of using an app-specific password, you can use\n> +OAuth2.0 authentication with Gmail. OAuth2.0 is more secure than\n> +app-specific passwords, and works regardless of whether you have multi-factor\n> +authentication set up.\n\nThanks. Much nicer.\n"},{"id":"519297","messageId":"xmqq5xhhepbs.fsf@gitster.g","threadId":"63454","inReplyTo":"PN3PR01MB95974BABA153882DE494D06EB861A@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM","subject":"Re: [PATCH v5 2/4] docs: improve formatting in git-send-email documentation","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-05-30T21:55:19Z","receivedAt":"2025-05-30T21:55:22Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Aditya Garg writes:\n\n> Thats definitely much better. Although, not really in the scope\n> of this patch series ;)\n\nI agree. As you decided not to touch this part with your series, it\nis perfectly fine to leave it as-is. Your series is not making this\npart any worse that way.\n"}]}