All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Greg KH <gregkh@suse.de>, Ingo Molnar <mingo@elte.hu>,
	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: Wed, 11 Nov 2009 13:43:56 -0800	[thread overview]
Message-ID: <4AFB301C.3050800@zytor.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0911111211270.31845@localhost.localdomain>

On 11/11/2009 12:14 PM, Linus Torvalds wrote:
> 
> 
> On Wed, 11 Nov 2009, James Bottomley wrote:
>>
>> So, now that you're showing an interest in all of this, how about I send
>> you the final update hook to add to your tree?  It will produce less
>> latency than the cron job I run on kernel.org to pull your tree into one
>> I have here ever twenty minutes or so and run the hooks.
> 
> Quite frankly, I'd much rather not run hooks on my tree directly. The less 
> that can possibly get screwed up with my kernel.org tree, the happier I 
> am. So in many ways, I really prefer the whole "done separately by others" 
> approach.
> 
> But hey, send the hook to me, and I'll think about it.
> 

One thing we might be able to do is to create an "exploder hook" on your
tree - something that asynchronously broadcasts a notification that
anyone can subscribe to.

	-hpa


  reply	other threads:[~2009-11-11 21:44 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 [this message]
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
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=4AFB301C.3050800@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=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.