All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: David Dillow <dave@thedillows.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Greg KH <gregkh@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Chris Wright <chrisw@sous-sol.org>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [RFC] new -stable tag variant, Git workflow question
Date: Thu, 12 Nov 2009 11:50:45 -0800	[thread overview]
Message-ID: <4AFC6715.7000902@zytor.com> (raw)
In-Reply-To: <1258045292.5944.8.camel@lap75545.ornl.gov>

On 11/12/2009 09:01 AM, David Dillow wrote:
> On Thu, 2009-11-12 at 07:15 -0800, H. Peter Anvin wrote:
>> On 11/11/2009 11:45 PM, Ingo Molnar wrote:
>>>
>>> That's already possible via the git-commits-head@vger.kernel.org email 
>>> list. Anyone can subscribe to it and can procmail process it. It is also 
>>
>> There are a couple of disadvantages with this -- a hera -> vger -> hera
>> bounce, in particular (those two machines are nowhere close to each
>> other, and there can be huge latecy.)  For real-time robots running on
>> hera, a lower-latency mechanism would be useful.
> 
> Change the hook on hera that sends the email to use a local alias that
> includes git-commits-header@vger and a local list that processes on hera
> can subscribe to? That could avoid the bounce...

Not really... a lot of the bounce delay is due to mail processing on
hera itself.

	-hpa


  reply	other threads:[~2009-11-12 19:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10  3:48 [RFC] new -stable tag variant, Git workflow question Ingo Molnar
2009-11-10  4:14 ` Greg KH
2009-11-10  4:20   ` Ingo Molnar
2009-11-10 14:30     ` James Bottomley
2009-11-10 17:22       ` Ingo Molnar
2009-11-10 17:53         ` Linus Torvalds
2009-11-10 18:06           ` Ingo Molnar
2009-11-10 14:29   ` James Bottomley
2009-11-10 15:52     ` Stefan Richter
2009-11-10 19:12       ` Chris Friesen
2009-11-10 21:20         ` Ingo Molnar
2009-11-10 19:39       ` Greg KH
2009-11-10 20:45         ` Ingo Molnar
2009-11-10 21:11           ` Junio C Hamano
2009-11-10 21:25             ` Greg KH
2009-11-10 21:29             ` Ingo Molnar
2009-11-10 19:37     ` Greg KH
2009-11-10 20:39       ` Ingo Molnar
2009-11-11 18:50       ` James Bottomley
2009-11-11 20:00         ` Linus Torvalds
2009-11-11 20:06           ` James Bottomley
2009-11-11 20:14             ` Linus Torvalds
2009-11-11 21:43               ` H. Peter Anvin
2009-11-11 21:52                 ` Linus Torvalds
2009-11-12  7:45                   ` Ingo Molnar
2009-11-12 15:15                     ` H. Peter Anvin
2009-11-12 17:01                       ` David Dillow
2009-11-12 19:50                         ` H. Peter Anvin [this message]
2009-11-12 14:41                   ` James Bottomley
2009-11-12  4:41         ` Greg KH
2009-11-12 16:11           ` James Bottomley
2009-11-19 18:15             ` Greg KH

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=4AFC6715.7000902@zytor.com \
    --to=hpa@zytor.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=chrisw@sous-sol.org \
    --cc=dave@thedillows.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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.