public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

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>,
	linux-usb@vger•kernel.org, linux-serial@vger•kernel.org,
	devel@driverdev•osuosl.org
Subject: Movement of the USB, TTY, Staging, and driver core trees for linux-next
Date: Tue, 9 Nov 2010 09:23:21 -0800	[thread overview]
Message-ID: <20101109172321.GA10927@kroah.com> (raw)

Hi Stephen,

As discussed at the kernel summit, I've moved the USB, TTY, Staging, and
driver core trees into git instead of using quilt.

Previously you had been pulling in the quilt trees from kernel.org, so
this should hopefully be easier.

The location of the trees are now at:
 USB:
	git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6.git
	with the usb-next and usb-linus branches
 TTY:
	git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty-2.6.git
	with the tty-next and tty-linus branches
 driver core:
	git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core-2.6.git
	with the driver-core-next and driver-core-linus branches
 staging:
	git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6.git
	with the staging-next and staging-linus branches

Note the staging tree has moved from before, it used to be in a
staging-next-2.6.git/ tree, and now it is together with the main staging
development tree in just "staging-2.6.git/"

There are no known interdependancies between these trees, unlike my
previous quilt trees, so merges should be fine (if not, I should find
them as well.)

If there are any problems with this, please let me know.

thanks,

greg k-h

                 reply	other threads:[~2010-11-09 17:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20101109172321.GA10927@kroah.com \
    --to=greg@kroah$(echo .)com \
    --cc=devel@driverdev$(echo .)osuosl.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-serial@vger$(echo .)kernel.org \
    --cc=linux-usb@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox