From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 23 Sep 2014 22:46:32 +0200 Subject: [Buildroot] [PATCH 1/1] ympd: new package In-Reply-To: References: <1411502012-13553-1-git-send-email-limpens@gmail.com> <20140923220220.435839a5@free-electrons.com> Message-ID: <20140923224632.17a49f30@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Eric Limpens, Please keep the Buildroot list in Cc. On Tue, 23 Sep 2014 22:28:10 +0200, Eric Limpens wrote: > should I set the current patch to 'superseded' in patchwork? I'll send a > new/revised version. We usually set the state to "Superseded" once a new patch has been sent. If we have requested some changes and we are fairly sure the submitter is going to submit an updated version, then we usually set the state to "Changes requested". But in fact, it doesn't make much difference, as in both cases, the patch is no longer in the "New" state, which means we no longer consider it as to be merged. Thanks, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com