mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
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:52:46 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.01.0911111350290.31845@localhost.localdomain> (raw)
In-Reply-To: <4AFB301C.3050800@zytor.com>



On Wed, 11 Nov 2009, H. Peter Anvin wrote:
> > 
> > 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.

Yeah, some minimal hook just informing any interested party about "ok, 
Linus pushed to the main tree" (and in fact, perhaps generalized so that 
you can show that you are interested in some particular branch of _any_ 
tree that people can just add to their trees) certainly doesn't sound like 
a bad idea.

That way we can get rid of "polling by cron", without having to have the 
tree owners themselves care about who is interested in exactly what..

			Linus

  reply	other threads:[~2009-11-11 21:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10  3:48 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 [this message]
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=alpine.LFD.2.01.0911111350290.31845@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --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=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

Powered by JetHome