From: Bryan Hundven <bryanhundven@gmail.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Long-term stable versions in linux-2.6-stable.git?
Date: Wed, 1 Jun 2011 17:06:18 -0700 [thread overview]
Message-ID: <BANLkTinxbqs1gHMSv5YPF0fCK1AOiCXTwg@mail.gmail.com> (raw)
In-Reply-To: <20110601225723.GA18471@suse.de>
On Wed, Jun 1, 2011 at 3:57 PM, Greg KH <gregkh@suse.de> wrote:
> On Wed, Jun 01, 2011 at 03:33:21PM -0700, Bryan Hundven wrote:
>> On Wed, Jun 1, 2011 at 2:15 PM, Greg KH <gregkh@suse.de> wrote:
>> > On Wed, Jun 01, 2011 at 10:38:35AM -0700, Bryan Hundven wrote:
>> >> Hello,
>> >>
>> >> I was wondering if there are plans to include the long-term stable
>> >> versions in the /pub/scm/linux/kernel/git/stable/linux-2.6-stable.git
>> >> repository?
>> >>
>> >> I'm not subscribed to lkml, please cc on response.
>> >
>> > It's been discussed numerous times in the past, the thing is, I don't
>> > control the script that does this so I have no control over it, sorry.
>>
>> Ok. The reason I ask is that it is painful to merge changes from
>> 2.6.35.13 back to 2.6.35.9, then forward to >2.6.36, although I guess
>> I will have to live with it.
>
> Why would you have to do that? Why can't you just create the tree
> yourself by pulling from the different longterm branches?
That works too. Thank you!
>> If you don't mind me asking; who controls the script that does this?
>
> I really don't know, sorry.
>
prev parent reply other threads:[~2011-06-02 0:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 17:38 Bryan Hundven
2011-06-01 21:15 ` Greg KH
2011-06-01 22:33 ` Bryan Hundven
2011-06-01 22:57 ` Greg KH
2011-06-02 0:06 ` Bryan Hundven [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=BANLkTinxbqs1gHMSv5YPF0fCK1AOiCXTwg@mail.gmail.com \
--to=bryanhundven@gmail.com \
--cc=gregkh@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®