linux-next: Tree for Sep 30

* linux-next: Tree for Sep 30
@ 2013-09-30 10:20 Thierry Reding
  2013-10-12 20:30 ` Stephen Rothwell
  0 siblings, 1 reply; 14+ messages in thread
From: Thierry Reding @ 2013-09-30 10:20 UTC (permalink / raw)
  To: linux-next, linux-kernel; +Cc: Mark Brown

[-- Attachment #1: Type: text/plain, Size: 2600 bytes --]

Hi all,

As I'm sure is the case for many of us, I've become very dependent upon
the linux-next tree. So everytime Stephen goes on vacation I break out
in a cold sweat.

Here's my attempt at providing temporary service until Stephen is back.
The result is likely a lot worse than what you're used to. Going through
this made me appreciate what Stephen does even more.

I've uploaded today's tree to a git repository here:

	git://gitorious.org/thierryreding/linux-next.git

There's a master branch with today's tree and a next-20130930 tag as
usual. One notable difference to Stephen's linux-next trees is the
omission of the mmotm patches because I haven't had the time to come up
with the proper scripting for that.

I took some notes about conflicts, but I lack any contact information
for the trees so unless I can scrape some useful information from the
MAINTAINERS file I will just have to send them out to LKML and hope that
the right people look at them.

Test builds of the i386 and x86_64 default configurations don't show any
breakage so far. Provided there's time I may run a test build for ARM
default configurations, but I don't have the resources to do much more
than that. It'd be great if others could help out with the testing. Note
that I haven't run any build tests in between merges, only on the final
tree.

To keep expectations reasonably low, I will not be able to do this every
day, but I'll try to do the linux-next tree as often as I can. If anyone
is interested in helping out, I've included various scripts that I used
in the Next directory:

	- setup: creates remotes for all trees listed in Next/Trees
	- fetch: fetches from all the trees listed in Next/Trees
	- merge: merges all trees in Next/Trees

The fetch and merge scripts assume that the setup script has already
been run. If a merge conflict happens, the merge script will drop you to
a subshell. Once any issues are resolved and the result committed, you
can exit the subshell and the merge will continue where it left off.

In case anyone is interested in doing one of the trees, please let me
know so there's no duplication of work. Mark Brown volunteered to share
the load, but I'm sure we could use more volunteers to make it easier on
all of us.

Hosting of the repository may be a problem. I've requested an account on
kernel.org on Friday, which is obviously somewhat on short notice, and
not everyone might have an account on gitorious. I guess we'll just have
to work with what we have and see how it goes. Unfortunately this
implies that the URL of the tree may change between daily trees.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread