[Buildroot] [PATCH 1/1] wiringpi: bump version to 8d188fa0e00bb8c6ff6eddd07bf92857e9bd533a

[Carlos Santos]

> From: "Baruch Siach" <baruch at tkos.co.il>
> To: "Atanas Palavrov" <palavrov at gmail.com>
> Cc: "Peter Seiderer" <ps.report at gmx.net>, "buildroot" <buildroot at buildroot.org>
> Sent: Friday, June 22, 2018 8:20:49 AM
> Subject: Re: [Buildroot] [PATCH 1/1] wiringpi: bump version to 8d188fa0e00bb8c6ff6eddd07bf92857e9bd533a

> Hi Atanas,
> 
> On Fri, Jun 22, 2018 at 12:15:59PM +0200, Atanas Palavrov wrote:
>> Well, seems that I did a mess with the new email in patchwork. My idea was
>> to reuse `git send-mail`.
>> I’m attaching the same patch here to discover if patchwork will be smart
>> enough to update the existing patch - didn’t get how to use it from the docs
>> ...
> 
> You can't update the content of an existing patchwork entry.
> 
> The usual procedure is to send another patch that is marked in the subject
> line as v2, v3, etc. You can use the -v command line parameter of 'git
> send-email' (actually 'git format-patch') for that.
> 
> Then, you update the status of the previous patch to 'Superseded'. You need to
> create an account for yourself on patchwork using the same email address as
> the sender of the patch. This would allow you to change the status of your
> patches on patchwork.

You can also link additional email addresses, so you can use both work
and personal email accounts. This is also useful if you move to another
job or your company changes the domain name, like recently happened with
Free Electrons, which was renamed to Bootlin.

-- 
Carlos Santos (Casantos) - DATACOM, P&D
“Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.” — Epitaph of a volunteer