From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Login to patchwork to mark patches as superseded
Date: Sun, 30 May 2021 12:22:52 +0200 [thread overview]
Message-ID: <d3446a33-5067-be7c-dd37-333d48fd0ac6@ipfire.org> (raw)
In-Reply-To: <773e2956-0af5-25f1-21e8-de6c4e313a4f@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
Hello Adolf,
thanks for your message.
Yes, marking patches as being superseded if their author submits a new version of them is
a manual task. (Sometimes, Patchwork also looses track and marks staged or applied patches
as still being "new". We unfortunately never really figured out why that is. :-/ )
Personally, I am going through my patches listed at Patchwork every now and then, and add
labels (superseded, applied, etc.) to patches needing them. Not sure if someone else besides
me does this, but since Michael will have that entire enormous blob in his inbox sooner or
later, I guess cleaning that list up a bit helps. :-)
I am surprised to learn your IPFire people credentials don't work there. Mine do...
Thanks, and best regards,
Peter Müller
> Hi All,
>
> I have seen communications recently where a person was asked to login to Patchwork and mark old patches as superseded.
>
> If this is something I should not be doing myself then no problems, I will stay with what I am doing.
>
> If I am supposed to be doing that, how do I login to Patchwork. I tried logging in using my credentials from IPFire People and from IPFire Bugzilla. In both cases it said my username or password were incorrect.
>
> Regards,
>
> Adolf.
>
next prev parent reply other threads:[~2021-05-30 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 20:23 Adolf Belka
2021-05-30 10:22 ` Peter Müller [this message]
2021-05-30 14:54 ` Adolf Belka
[not found] <01044895-14CA-4FDF-94B2-C501D0679F81@ipfire.org>
2021-06-02 20:32 ` Peter Müller
2021-06-02 21:20 ` Adolf Belka
2021-08-05 21:28 ` Adolf Belka
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=d3446a33-5067-be7c-dd37-333d48fd0ac6@ipfire.org \
--to=peter.mueller@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