public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: Michael Tremer <michael.tremer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Problem trying to logout from patchwork
Date: Sun, 14 Sep 2025 12:43:52 +0200	[thread overview]
Message-ID: <d132f0de-2a84-4d94-a700-495c2255da08@ipfire.org> (raw)
In-Reply-To: <06CE305E-664C-4DE2-AB0A-FD0353391B12@ipfire.org>

Hi Michael,

On 14/09/2025 12:36, Michael Tremer wrote:
> Hello,
> 
> Thank you for reminding me.
> 
> This seems to be a bug in Patchwork:
> 
>    https://git.ipfire.org/?p=thirdparty/patchwork.git;a=commitdiff;h=45f47e96c6c90aefac37b02e0e15052f6ba41a90
> 
> We are already on the latest version and this patch is not part of a tagged release, yet. So I have manually applied this change.

Yaaah. I am logged out.

Regards,

Adolf.

> 
> Best,
> -Michael
> 
>> On 14 Sep 2025, at 10:50, Adolf Belka <adolf.belka@ipfire.org> wrote:
>>
>> Hi Michael,
>>
>> On 04/09/2025 14:29, Adolf Belka wrote:
>>> Hi All,
>>> I logged into patchwork to change the status of a patch I submitted. That worked fine.
>>> However, when I then tried to logout I got the following message in my browser screen
>>> --------------------
>>> Looks like there’s a problem with this site
>>> https://patchwork.ipfire.org/user/logout/ sent back an error.
>>> Error code: 405 Method Not Allowed
>>>      Check to make sure you’ve typed the web site address correctly.
>>> --------------------
>>
>> You probably missed this while you had limited access. Currently I still can't logout from patchwork.
>>
>> Regards,
>>
>> Adolf.
>>
>>
>>> Regards,
>>> Adolf.
>>
>>
> 



      reply	other threads:[~2025-09-14 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 12:29 Adolf Belka
2025-09-14  9:50 ` Adolf Belka
2025-09-14 10:36   ` Michael Tremer
2025-09-14 10:43     ` Adolf Belka [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=d132f0de-2a84-4d94-a700-495c2255da08@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=michael.tremer@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