From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Frank Schäfer" <fschaefer.oss@googlemail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Patch update notification: 4 patches updated
Date: Sat, 22 Dec 2012 14:45:29 -0200 [thread overview]
Message-ID: <20121222144529.2727c94f@redhat.com> (raw)
In-Reply-To: <50D5C37A.1030303@googlemail.com>
Em Sat, 22 Dec 2012 15:28:10 +0100
Frank Schäfer <fschaefer.oss@googlemail.com> escreveu:
> Am 22.12.2012 00:28, schrieb Patchwork:
> > Hello,
> >
> > The following patches (submitted by you) have been updated in patchwork:
> >
> > * em28xx: msi Digivox ATSC board id [0db0:8810]
> > - http://patchwork.linuxtv.org/patch/15792/
> > was: New
> > now: RFC
> >
> > * em28xx: msi Digivox ATSC board id [0db0:8810]
> > - http://patchwork.linuxtv.org/patch/15783/
> > was: New
> > now: RFC
> >
> > * em28xx: msi Digivox ATSC board id [0db0:8810]
> > - http://patchwork.linuxtv.org/patch/15773/
> > was: New
> > now: RFC
> >
> > * em28xx: msi Digivox ATSC board id [0db0:8810]
> > - http://patchwork.linuxtv.org/patch/15764/
> > was: New
> > now: RFC
>
> All these patches are superseeded.
They're just discussions, and proposed patches (AKA: RFC).
So, they were tagged as such. I use superseded when a new version of a
normal patch is in patchwork. RFC is used there for patches meant for someone
to test and give a feedback. That's the case of those all 4 patches.
In any case, the practical effect is that patches that aren't "New" or
"Under review" don't appear on my quilt queue anymore.
Regards,
Mauro
>
> Regards,
> Frank
--
Cheers,
Mauro
prev parent reply other threads:[~2012-12-22 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121221232803.27830.79186@www.linuxtv.org>
2012-12-22 14:28 ` Patch update notification: 4 patches updated Frank Schäfer
2012-12-22 16:45 ` Mauro Carvalho Chehab [this message]
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=20121222144529.2727c94f@redhat.com \
--to=mchehab@redhat.com \
--cc=fschaefer.oss@googlemail.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.