All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: [ANNOUNCE] patchwork notifications
Date: Wed, 01 Aug 2012 13:42:49 -0300	[thread overview]
Message-ID: <50195C89.5090808@redhat.com> (raw)

Hi Developers,

Just to let you know, I finally made patchwork notifications to work.

With this change, every time a patch (or a group of patches) have their
status changed, an email will be sent to the patch author, similar to this one:

	The following patches (submitted by you) have been updated in patchwork:

	 * [43/47,media] mt2063: add some useful info for the dvb callback calls
	     - http://patchwork.linuxtv.org/patch/9332/
	    was: New
	    now: RFC

	 * [2/4,media] DocBook/dvbproperty.xml: Fix ISDB-T delivery system parameters
	     - http://patchwork.linuxtv.org/patch/9557/
	    was: New
	    now: Accepted

	 * [13/35,media] az6007: need to define drivers name before including dvb-usb.h
	     - http://patchwork.linuxtv.org/patch/9593/
	    was: New
	    now: Accepted

...

Developers that don't want this feature can opt-out, using this link:
	 http://patchwork.linuxtv.org/mail/

Still, I suggest you to don't to that ;)

As a reminder, the policy I'm using to handle patches is:

New patches are marked there as 'New'.

When I'm expecting someone (typically, the driver's author) to review a patch, the
status is changed to 'Under review'. Unfortunately, patchwork doesn't have a field
to indicate to whom, so I'm currently this information on a separate file on my local
machine.

When the same patch is sent twice, or a new version of the same patch and I am
able to identify it, the old patch is marked as  'superseded'.

When someone asks for changes at the patch, the patch is marked as 'changes requested'.

When the patch is wrong or doesn't apply, it is marked as 'rejected'. Most of the
time, 'rejected' and 'changes requested' means the same thing for the developer:
he'll need to re-work on the patch.

Patches that aren't meant to be applicable at the media-tree.git are typically
marked as 'not applicable' [1].

Finally, when everything is ok and it got applied either at the main tree or at
the fixes tree, the patch is marked as 'accepted'.

Of course, as we're all humans (and patchwork status is changed manually by me),
errors may happen. Feel free to ping me on irc or via email on such cases.

[1] Just to make my life easier, patches for a few other random trees that I
maintain/partially maintain, like media-build tree, are generally marked as 
'Accepted' as well, when I am the one applying it, as it saves me time ;)

I hope you'll find this new tool useful.

Regards,
Mauro

                 reply	other threads:[~2012-08-01 17:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=50195C89.5090808@redhat.com \
    --to=mchehab@redhat.com \
    --cc=linux-media@vger.kernel.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 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.