From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: tty tree change for linux-next
Date: Fri, 31 Jul 2009 21:39:05 -0700 [thread overview]
Message-ID: <20090801043905.GA12779@kroah.com> (raw)
Hi Stephen,
I've now merged Alan's tty tree into my patch trees, and I'd like to ask
for linux-next to pick them up.
They are contained within the same directory as my other trees (staging,
usb, driver-core), and conviently named "tty.current" and "tty", and can
be found at:
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
As you can see by the nameing in the above directory, the usb and
staging trees changed names by virtue of putting the tty tree ahead of
them. Your scripts might need adjusting for this.
If there are any problems with the trees, please let me know.
thanks,
greg k-h
next reply other threads:[~2009-08-01 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 4:39 Greg KH [this message]
2009-08-01 6:41 ` tty tree change for linux-next Stephen Rothwell
2009-08-01 7:22 ` Stephen Rothwell
2009-08-01 17:18 ` Greg KH
2009-08-01 23:16 ` Stephen Rothwell
2009-08-05 17:08 ` 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=20090801043905.GA12779@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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