From: Greg Kurz <groug@kaod.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] 9pfs: disable msize warning for synth driver
Date: Tue, 8 Sep 2020 11:34:28 +0200 [thread overview]
Message-ID: <20200908113428.58c6dcb4@bahia.lan> (raw)
In-Reply-To: <4834247.Ya9cJq7G5r@silver>
On Tue, 08 Sep 2020 11:01:15 +0200
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
> On Dienstag, 8. September 2020 10:10:36 CEST Greg Kurz wrote:
> > > > BTW, have you ever tried dealing with patchwork client's 'state' feature
> > > > for already transmited patches on the list (new, rejected, etc.)?
> > >
> > > Nope, never used patchwork's state at all and I've no idea on how it
> > > works... but I can ask to my former IBM colleagues at Ozlabs.
> >
> > It seems that you need to be a "maintainer" from a patchwork standpoint
> > to manipulate patch states.
> >
> > https://patchwork.readthedocs.io/en/latest/usage/overview/#maintainers
> >
> > ===========
> > Maintainers
> >
> > Maintainers are a special type of user that with permissions to do
> > certain operations that regular Patchwork users can’t. Patchwork
> > maintainers usually have a 1:1 mapping with a project’s code
> > maintainers though this is not necessary.
> >
> > The operations that a maintainer can invoke include:
> >
> > Change the state of a patch
> > Archive a patch
> > Delegate a patch, or be delegated a patch
> > ===========
> >
> > No clue how to upgrade to maintainer though...
>
> The command to change a patch state is, e.g.:
>
> pwclient update -s Queued 11759645
>
> When I do that I get this error:
>
> The update action requires authentication, but no username or password
> is configured
>
> So looks like it would require somebody to create an account somewhere,
> wherever that is.
>
Which patchwork site are you using ?
https://patchwork.ozlabs.org/ or https://patchwork.kernel.org/ ?
Anyway, both support self account creation:
https://patchwork.ozlabs.org/register/
https://patchwork.kernel.org/register/
This allows you to update your own patches, but you need
to be maintainer to update other's.
> Best regards,
> Christian Schoenebeck
>
>
next prev parent reply other threads:[~2020-09-08 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 16:50 [PATCH] 9pfs: disable msize warning for synth driver Christian Schoenebeck
2020-09-07 9:57 ` [SPAM] " Greg Kurz
2020-09-07 11:55 ` Christian Schoenebeck
2020-09-07 12:27 ` Greg Kurz
2020-09-08 8:10 ` Greg Kurz
2020-09-08 9:01 ` Christian Schoenebeck
2020-09-08 9:34 ` Greg Kurz [this message]
2020-09-08 10:03 ` Christian Schoenebeck
2020-09-08 11:02 ` Christian Schoenebeck
2020-09-08 9:54 ` Christian Schoenebeck
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=20200908113428.58c6dcb4@bahia.lan \
--to=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).