From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Fri, 7 Dec 2018 12:15:59 +0100 Subject: [Buildroot] [PATCH] pcm-tools: new package In-Reply-To: <1017622378.1606234.1544146335281.JavaMail.zimbra@datacom.com.br> References: <20180123140324.20801-1-casantos@datacom.ind.br> <20180123140324.20801-2-casantos@datacom.ind.br> <20180401161654.6412d152@windsurf> <1919985279.1291627.1522720961448.JavaMail.zimbra@datacom.ind.br> <1017622378.1606234.1544146335281.JavaMail.zimbra@datacom.com.br> Message-ID: <20181207121559.7e1b11e4@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello Carlos, On Thu, 6 Dec 2018 23:32:15 -0200 (BRST), Carlos Santos wrote: > Superseded-by: https://patchwork.ozlabs.org/patch/1009149/ I am wondering: is this Superseded-by really understood by patchwork to make a patch as Superseded? I don't see Superseded-by used in the patchwork code base. I see that the patch was marked as Superseded in patchwork, was it done manually by you, or automatically thanks to this e-mail ? If it was done manually by you, then I think it's not really useful to send this Superseded-by e-mail: we see in patchwork the latest version anyway, which is what is important. Thanks! Thomas -- Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com