All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: Patchwork: "maintainer status"
Date: Mon, 21 Oct 2019 22:06:38 +0200	[thread overview]
Message-ID: <20191021200638.GG25052@breakpoint.cc> (raw)
In-Reply-To: b9eff5ae-88ed-8759-f08c-ed6e7499917d@tessares.net

[-- Attachment #1: Type: text/plain, Size: 904 bytes --]

Matthieu Baerts <matthieu.baerts(a)tessares.net> wrote:
> I contacted Patchwork maintainers and it seems they are OK to add MPTCP to
> the list of projects.

Thanks Matthieu.

> But they are asking 2 questions:
> 
> > - do you want all of your team to have maintainer status in patchwork?
> (ie, should they all be able to update patch states?)
> 
> I don't know exactly who would need to have this. I guess everybody who did
> a review with an "accept" ("LGTM") should be able to directly change the
> status, no?

Note that anyone who has a patchwork account can change patch status of
changes they submitted themselves.

> Patchwork maintainers are asking me to give them a list of usernames. With
> the web interface, I can only get your user ID and email address but not
> your username. May you reply to me in private (or to the list) with your
> username?

Mine is "strlen".

             reply	other threads:[~2019-10-21 20:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 20:06 Florian Westphal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-21 20:12 [MPTCP] Re: Patchwork: "maintainer status" Mat Martineau
2019-10-22  7:55 Paolo Abeni
2019-10-22  8:25 Matthieu Baerts
2019-10-22  8:34 Matthieu Baerts
2019-10-22  8:36 Matthieu Baerts
2019-10-22  8:45 Matthieu Baerts
2019-10-22 21:28 Mat Martineau
2019-10-23  7:39 Matthieu Baerts
2019-10-23 20:38 Peter Krystad
2019-10-24  3:59 Matthieu Baerts
2019-11-04 13:56 Matthieu Baerts

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=20191021200638.GG25052@breakpoint.cc \
    --to=unknown@example.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.