All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: "Hans Verkuil" <hverkuil@xs4all.nl>,
	"Frank Schäfer" <fschaefer.oss@googlemail.com>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: RFC: First draft of guidelines for submitting patches to linux-media
Date: Mon, 10 Dec 2012 19:45:40 +0200	[thread overview]
Message-ID: <50C61FC4.7090100@iki.fi> (raw)
In-Reply-To: <20121210153816.0d4d9b64@redhat.com>

On 12/10/2012 07:38 PM, Mauro Carvalho Chehab wrote:
> Yeah, the issue is that both reviewed, non-reviewed and rejected/commented
> patches go into the very same queue, forcing me to revisit each patch again,
> even the rejected/commented ones, and the previous versions of newer patches.
>
> By giving rights and responsibilities to the sub-maintainers to manage their
> stuff directly at patchwork, those patches that tend to stay at patchwork for
> a long time will likely disappear, and the queue will be cleaner.

Is there any change module maintainer responsibility of patch could do 
what ever he likes to given patch in patchwork?

I have looked it already many times but I can drop only my own patches. 
If someone sends patch to my driver X and I pick it up my GIT tree I 
would like to mark it superseded for patchwork (which is not possible 
currently).

regards
Antti

-- 
http://palosaari.fi/

  reply	other threads:[~2012-12-10 17:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 13:07 RFC: First draft of guidelines for submitting patches to linux-media Hans Verkuil
2012-12-10 15:56 ` Frank Schäfer
2012-12-10 16:27   ` Hans Verkuil
2012-12-10 17:38     ` Mauro Carvalho Chehab
2012-12-10 17:45       ` Antti Palosaari [this message]
2012-12-10 18:43         ` Mauro Carvalho Chehab
2012-12-10 19:17       ` Frank Schäfer
2012-12-10 19:40         ` Mauro Carvalho Chehab
2012-12-11 20:41           ` Frank Schäfer
2012-12-10 18:33 ` Mauro Carvalho Chehab
2012-12-10 23:52   ` Laurent Pinchart
2012-12-11 10:29     ` Mauro Carvalho Chehab
2012-12-11 11:39       ` Laurent Pinchart
2012-12-11 12:59         ` Mauro Carvalho Chehab
2012-12-11 11:50       ` Hans Verkuil
2012-12-11 12:20         ` Laurent Pinchart
2012-12-11 15:13           ` Mauro Carvalho Chehab
2012-12-11 14:31         ` Mauro Carvalho Chehab
2012-12-11 13:15 ` Hans Verkuil
2012-12-11 15:17   ` Mauro Carvalho Chehab

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=50C61FC4.7090100@iki.fi \
    --to=crope@iki.fi \
    --cc=fschaefer.oss@googlemail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.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.