public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-media@vger.kernel.org, linuxtv-commits@linuxtv.org,
	Darren Hart <dvhltc@us.ibm.com>,
	Mikael Pettersson <mikpe@it.uu.se>,
	Thomas Gleixner <tglx@linutronix.de>,
	Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: [git:v4l-dvb/master] futex_lock_pi() key refcnt fix
Date: Sat, 06 Mar 2010 12:14:54 -0300	[thread overview]
Message-ID: <4B92716E.3080905@redhat.com> (raw)
In-Reply-To: <1267887010.4997.57.camel@laptop>

Peter Zijlstra wrote:
> Why is linuxtv sending crap like this?
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Sorry!

There's an post update hook script that sends an email to the patch author/SOB's 
for the new patches added at v4l-dvb git tree. Unfortunately, the git mailbomb 
script is doing something wrong: it is handling badly all the upstream patches 
that  were merged back on it. I'll need to figure out a way for it to exclude 
patches that got merged from the normal posts.

For now, I've stopped the exim process at the server. 

-- 

Cheers,
Mauro

      reply	other threads:[~2010-03-06 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NnuyF-0001D8-AC@www.linuxtv.org>
2010-03-06 14:50 ` [git:v4l-dvb/master] futex_lock_pi() key refcnt fix Peter Zijlstra
2010-03-06 15:14   ` 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=4B92716E.3080905@redhat.com \
    --to=mchehab@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=dvhltc@us.ibm.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linuxtv-commits@linuxtv.org \
    --cc=mikpe@it.uu.se \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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