From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Marvin Häuser" <mhaeuser@posteo.de>, git@vger.kernel.org
Subject: Re: [BUG] send-email propagates "In-Reply-To"
Date: Sun, 22 Aug 2021 19:11:26 +0700 [thread overview]
Message-ID: <41f4f8da-e3ca-9b66-66f1-e319a0428a2e@gmail.com> (raw)
In-Reply-To: <4db7759c-2123-533b-9f89-954c07f5832a@posteo.de>
On 22/08/21 16.24, Marvin Häuser wrote:
> I wrote a quick patch to adjust 2.1. to 3.1. [3]. I have no time right
> now to review the submission guidelines (and thus did not submit the
> patch "properly" yet), but I will try to get to that tonight or some
> time next week. If in the mean time you could provide any feedback on
> the behaviour or the patch, so that I can get things right the first
> time, that would be great!
>
> [3]
> https://github.com/mhaeuser/git/commit/d87f49a02c0efa3084ae6c70bbf583b865744e43
>
Since you have your desired commits queued on your fork (and thus
already use GitHub flow), you can open a PR targeting [1] and let
GitGitGadget prepare and send corresponding patch to git@vger.kernel.org
(this ML).
Or better learn to use `git format-patch` and `git send-email` - some
projects (including Git and Linux kernel) prefers contributions to be
submitted through mailing lists (email-style approach). Git for Windows
have nice guide to submit patches email-style at [2].
[1]: https://github.com/gitgitgadget/git
[2]:
https://github.com/git-for-windows/git/blob/main/CONTRIBUTING.md#submit-your-patch
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-08-22 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 9:24 [BUG] send-email propagates "In-Reply-To" Marvin Häuser
2021-08-22 12:11 ` Bagas Sanjaya [this message]
2021-08-23 16:35 ` Jeff King
2021-08-23 17:44 ` Marvin Häuser
2021-08-23 18:27 ` Jeff King
2021-08-23 21:47 ` Marvin Häuser
2021-08-24 7:48 ` Carlo Marcelo Arenas Belón
2021-08-25 0:15 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41f4f8da-e3ca-9b66-66f1-e319a0428a2e@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=mhaeuser@posteo.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).