From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 5 Dec 2017 13:43:22 +0100 Subject: [Buildroot] [PATCH v3] tcfagent: new package In-Reply-To: References: <20171204114306.28242-1-nolange79@gmail.com> <20171204120912.9850-1-nolange79@gmail.com> <20171205094143.GA4275@gmail.com> Message-ID: <20171205134322.6aae8e03@windsurf.lan> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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 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