From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Patchwork
Date: Tue, 29 Nov 2016 18:36:59 +0100 [thread overview]
Message-ID: <a9b0c71c-4da0-3fbe-064c-5ac8986e16e8@ipfire.org> (raw)
In-Reply-To: <1480433534.13949.71.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
Hi,
on my behalf, also: thanks to Jonatan!
I could have done this by myself but I was never really sure, which
patches I should mark 'superseded' and which not. What rules can I
follow? Exactly *when* can I mark a patch this way?
Best,
Matthias
On 29.11.2016 16:32, Michael Tremer wrote:
> Hi,
>
> just as a reminder, I would like to say that I very much support this.
>
> Patchwork is not "just another project" were the patches are and should rot. It
> is supposed to help us keeping things tidy and have a clue about what has been
> submitted and reviewed by whom.
>
> Thank you Jonatan for going through this and cleaning up after us all. I dearly
> hope that we will be able to keep this tidier from now on.
>
> Best,
> -Michael
>
> On Wed, 2016-11-09 at 15:27 +0100, Jonatan Schlag wrote:
>> Hi,
>> some members of this list got or will get some emails from our patchwork and
>> maybe wonder why the patches were superseded.
>> I will try to explain why these emails were sent out.
>> I updated some (i think around 20 to 30) patches, because
>> - the version in git is newer than the version of the the patch or
>> - there is a new version of this patch or
>> - the patch was not correctly caught from the mail (There were 2 patches this
>> happen) and so the patch was more than one time in patchwork or
>> - the patch belong to dnsmasq
>>
>> Regards Jonatan
>
prev parent reply other threads:[~2016-11-29 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1478701645.5695.0@mail01.ipfire.org>
2016-11-29 15:32 ` Patchwork Michael Tremer
2016-11-29 17:36 ` Matthias Fischer [this message]
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=a9b0c71c-4da0-3fbe-064c-5ac8986e16e8@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox