From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Ian Pilcher <i.pilcher@comcast.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFQ] Rules for accepting patches into the linux-releases tree
Date: Fri, 04 Mar 2005 23:52:32 -0600 [thread overview]
Message-ID: <1110001952.8498.10.camel@localhost> (raw)
In-Reply-To: <d0bejc$r11$1@sea.gmane.org>
On Fri, 2005-03-04 at 23:08 -0600, Ian Pilcher wrote:
> Greg KH wrote:
> > Anything else anyone can think of? Any objections to any of these?
> > I based them off of Linus's original list.
>
> Must already be in Linus tree (i.e. 2.6.X+1)?
No, it's cleaner in bitkeeper terms for the patches to be pulled into
the linux-releases tree first, and then Linus pulls from that. Linus
has said that that is what he intends to do.
Shaggy
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2005-03-05 6:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 22:21 [RFQ] Rules for accepting patches into the linux-releases tree Greg KH
2005-03-05 5:08 ` Ian Pilcher
2005-03-05 5:52 ` Dave Kleikamp [this message]
2005-03-05 8:19 ` Valdis.Kletnieks
2005-03-05 12:39 ` Ed Tomlinson
2005-03-05 9:58 ` Adam Sampson
2005-03-05 17:42 ` Greg KH
2005-03-05 18:26 ` Randy.Dunlap
2005-03-05 10:43 ` Andries Brouwer
2005-03-05 17:42 ` Greg KH
2005-03-06 17:10 ` Andres Salomon
2005-03-06 20:10 ` Adam Kropelin
2005-03-07 8:32 ` Andres Salomon
2005-03-07 7:50 ` Paul Jackson
2005-03-07 8:14 ` Andres Salomon
2005-03-05 13:59 ` Adrian Bunk
2005-03-05 17:40 ` Greg KH
2005-03-05 18:31 ` Andre Tomt
2005-03-05 20:01 ` Ian Pilcher
2005-03-06 9:44 ` Marcelo Tosatti
2005-03-07 17:35 ` John W. Linville
2005-03-06 11:20 ` Joel Becker
2005-03-06 11:23 ` Jesper Juhl
-- strict thread matches above, loose matches on Subject: below --
2005-05-19 6:25 [PATCH] I2C: lm80 driver improvement Greg KH
2005-03-05 5:57 ` [RFQ] Rules for accepting patches into the linux-releases tree Shawn Starr
2005-03-05 6:11 ` Randy.Dunlap
2005-03-05 16:33 ` 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=1110001952.8498.10.camel@localhost \
--to=shaggy@austin.ibm.com \
--cc=i.pilcher@comcast.net \
--cc=linux-kernel@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.