From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Patchwork now connected to people.ipfire.org
Date: Thu, 21 Oct 2021 11:57:00 +0200 [thread overview]
Message-ID: <0378cde8-8105-2ef1-a168-5b464b8952ae@ipfire.org> (raw)
In-Reply-To: <BCC341A6-B265-4DC7-9C6E-3B09F593265F@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
Hi Michael,
On 20/10/2021 23:46, Michael Tremer wrote:
> Could you try again now?
Thanks very much, it is working now. I successfully changed the status
of two of my old patches to superseded.
Adolf.
>
>> On 20 Oct 2021, at 21:40, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Michael,
>>
>>> On 19/10/2021 17:58, Michael Tremer wrote:
>>> Very good. Thanks for testing. Happy patching :)
>>>>> On 19 Oct 2021, at 16:45, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>
>>>> Hi everyone,
>>>>
>>>> On 19/10/2021 16:57, Michael Tremer wrote:
>>>>> Hello everyone,
>>>>>
>>>>> As requested at the last conference call, I have enabled LDAP authentication on Patchwork.
>>>>>
>>>>> I would like to ask people to log in and confirm that it works.
>>>>
>>>> Yeah, login successful. 😁
>> Today I tried to change some patches to status superseded. However I got the message that I don't have the permissions to change the status of my patches.
>>
>> Adolf.
>>>>
>>>> Adolf.
>>>>
>>>>> If there are any problems with it, feel free to raise them here or create a bug report.
>>>>>
>>>>> Best,
>>>>> -Michael
--
Sent from my laptop
next prev parent reply other threads:[~2021-10-21 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 14:57 Michael Tremer
2021-10-19 15:45 ` Adolf Belka
2021-10-19 15:58 ` Michael Tremer
2021-10-20 20:40 ` Adolf Belka
2021-10-20 21:46 ` Michael Tremer
2021-10-21 9:57 ` Adolf Belka [this message]
2021-12-03 21:44 ` Adolf Belka
2021-12-04 12:45 ` Michael Tremer
2021-12-04 14:04 ` 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=0378cde8-8105-2ef1-a168-5b464b8952ae@ipfire.org \
--to=adolf.belka@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