From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Patchwork updates
Date: Mon, 25 Oct 2021 19:34:52 +0100 [thread overview]
Message-ID: <04C52A73-1F1D-459C-916C-81E30211FD96@ipfire.org> (raw)
In-Reply-To: <7ad2f06f-e723-0699-7508-482021b546ea@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
Hello Adolf,
Yes, that is okay.
Normally Patchwork should detect that automatically, but in quite a few cases, that goes wrong. Therefore it has to be done manually from time to time.
-Michael
> On 23 Oct 2021, at 12:33, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi everyone,
>
> I now have access to patchwork and I have been updating the status of my old patches to superseded or dropped or rejected as appropriate.
>
> I also see quite a few patches that are still marked as new but they have been merged or even released in a final Core Update. I just want to check that it is okay if I update those patches to either staged or accepted or if that type of status change should not be done by myself.
>
>
> Regards,
>
> Adolf.
>
prev parent reply other threads:[~2021-10-25 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 11:33 Adolf Belka
2021-10-25 18:34 ` Michael Tremer [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=04C52A73-1F1D-459C-916C-81E30211FD96@ipfire.org \
--to=michael.tremer@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