From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] tcfagent: new package
Date: Tue, 5 Dec 2017 13:43:22 +0100 [thread overview]
Message-ID: <20171205134322.6aae8e03@windsurf.lan> (raw)
In-Reply-To: <CADYdroPG1Sj3-vfDjWryXD4bdfE9oZ4VmPyDr9s7evBwwxZjHg@mail.gmail.com>
Hello,
On Tue, 5 Dec 2017 11:51:20 +0100, Norbert Lange wrote:
> Can do, but maybe scrap that part of your documentation:
> "You can also add the --in-reply-to <message-id> option when
> submitting a patch to the mailing list. The id of the mail to reply to
> can be found under the "Message Id" tag on patchwork. The advantage of
> in-reply-to is that patchwork will automatically mark the previous
> version of the patch as superseded."
Yeah, I'm not sure if that works really in practice. In addition,
almost nobody in the Buildroot community submits the new iteration of
a patch series as a reply to the previous one. I personally prefer to
see new iterations sent as new threads (but it's just a personal
preference).
Norbert: our documentation is part of the Git repository, so if you see
anything wrong or that needs to be improved, then patches are welcome!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-05 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 11:43 [Buildroot] [PATCH v2] tcfagent: new package Norbert Lange
2017-12-04 12:09 ` [Buildroot] [PATCH v3] " Norbert Lange
2017-12-05 9:41 ` Marcus Folkesson
2017-12-05 10:51 ` Norbert Lange
2017-12-05 12:43 ` Thomas Petazzoni [this message]
2017-12-13 13:49 ` Thomas Petazzoni
2017-12-15 13:11 ` Norbert Lange
2018-01-02 16:34 ` Norbert Lange
2018-01-02 16:57 ` Thomas Petazzoni
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=20171205134322.6aae8e03@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.