From: Vivan Garg <v.garg.work@gmail.com>
To: Victoria Dye <vdye@github.com>
Cc: Vivan Garg <gvivan6@gmail.com>,
git@vger.kernel.org, Emily Shaffer <nasamuffin@google.com>
Subject: Re: [PATCH] Documentation/MyFirstContribution: add setup template for git send-email
Date: Wed, 22 Feb 2023 21:09:46 -0700 [thread overview]
Message-ID: <CADupsJNVV+GqV9+On6rWiDfVE4ryCvtwzcLAN_GuDcysKXyACQ@mail.gmail.com> (raw)
In-Reply-To: <a6b0cf3b-af44-3d35-3de1-62aaf65f1543@github.com>
> It's generally good practice to CC contributors that have been recently
> and/or heavily involved in the code you're changing. Given that, I've CC'd
> Emily Shaffer (original author of the doc, including the section you'd like
> to change).
I see, will do in the future.
> Earlier commits related to this file start with just "MyFirstContribution:",
> so you can leave out the "Documentation/" prefix to stay under the 50
> character width.
Noted.
> The section you're replacing explicitly states that providing example
> configuration is out of scope for this document. That's for good reason; the
> example config you've provided isn't universal to all developer setups. It
> would be more confusing to a new contributor if we recommended a config
> that's incompatible with their setup than if we left it open-ended as it is
> now.
Oh, I thought you had to set these parameters, i.e. smtpServer, smtpServerPort,
smtpEncryption, smtpUser, and smtpPass in gitConfig regardless of the setup (I
did some googling as well). However, I'll take your word for it that it may be
incompatible with some setups. Thanks for pointing that out!
> However, if you still want to make the guidance in this section more
> specific, you could add a 'linkgit:git-config' link and note that the
> relevant SMTP configs are under the 'sendemail' section.
That sounds like a good addition! I'll do it then. Thanks!
next prev parent reply other threads:[~2023-02-23 4:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 1:13 [PATCH] Documentation/MyFirstContribution: add setup template for git send-email Vivan Garg
2023-02-22 21:18 ` Victoria Dye
2023-02-23 4:09 ` Vivan Garg [this message]
2023-02-23 5:40 ` [PATCH v2 0/1] MyFirstContribution: add note about SMTP server config Vivan Garg
2023-02-23 5:40 ` [PATCH v2 1/1] " Vivan Garg
2023-02-23 6:23 ` Victoria Dye
2023-02-23 6:24 ` [PATCH v2 0/1] " Victoria Dye
2023-02-23 6:47 ` Vivan Garg
2023-02-23 8:27 ` [PATCH v3] " Vivan Garg
2023-02-23 8:45 ` Benson Muite
2023-02-23 9:20 ` Vivan Garg
2023-02-23 10:37 ` Benson Muite
2023-02-26 0:49 ` Vivan Garg
2023-02-26 13:19 ` Bagas Sanjaya
2023-02-26 13:07 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADupsJNVV+GqV9+On6rWiDfVE4ryCvtwzcLAN_GuDcysKXyACQ@mail.gmail.com \
--to=v.garg.work@gmail.com \
--cc=git@vger.kernel.org \
--cc=gvivan6@gmail.com \
--cc=nasamuffin@google.com \
--cc=vdye@github.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).