Re: [GIT pull] x86 fixes for 2.6.26
From: Jesper Juhl
Date: Mon May 19 2008 - 20:01:45 EST
2008/5/19 Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>:
> On Mon, 19 May 2008, Jesper Juhl wrote:
>> Ok, thanks a lot. Now, I have one final question for you.
>> In order to be able to play around with the patches, see if they
>> apply, fix them up, test for merge conflicts etc etc, I obviously need
>> a tree with content, not just a bare tree. But I see on
>> master.kernel.org that all the published trees are bare trees.
> I think just about *everybody* does their own development on their own
> machine. I know I do, and I'm pretty certain that everybody else does too.
> Then we just upload the end result to master.kernel.org into a bare
> repository that is only used for exporting to others, never for anything
>> So, I assume I create a tree in my homedir like so;
>> $ git clone -l -s /pub/scm/linux/kernel/git/torvalds/linux-2.6.git /home/juhl/trivial-work-tree
>> create all the branches and do all the work in that one,
> You can do that, and actually work on master.kernel.org, but do you really
> want to?
Not if I can help it, no. I just couldn't work out from the git docs
how to do it otherwise when working with kernel.org and bare trees.
> Then, the easiest way to publish the result is to just create a bare
> repository on master.kernel.org, and push to it. And just make sure that
> you pre-populate that bare repo with my tree, so that when you push from
> your home machine, it only pushes the (smallish) actual changes!
> So the workflow I'd suggest is:
> - do all the work on your own hardware
> - create the initial (bare) kernel.org tree with
> cd /pub/scm/linux/kernel/git/juhl
> git clone --bare -l -s ../torvalds/linux-2.6 trivial-2.6
> - then just push to that tree from your own machine
> and voila, you're all done.
That worked beautifully. Thanks a lot.
Stephen: There is now a trivial-2.6.git tree at
with a 'next' branch that you can pull into linux-next, please.
Once we hit a merge window I'll rename the 'next' branch and ask Linus
to pull it, then create a new 'next'.
Jesper Juhl <jesper.juhl@xxxxxxxxx>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/