From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: linux-next: first tree
Date: Thu, 14 Feb 2008 15:26:21 -0600 [thread overview]
Message-ID: <1203024381.3158.26.camel@localhost.localdomain> (raw)
In-Reply-To: <47B4AC97.3040001@garzik.org>
On Thu, 2008-02-14 at 16:03 -0500, Jeff Garzik wrote:
> Stephen Rothwell wrote:
> > Also, more trees please ... :-)
>
> Please add the 'NEXT' branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>
> to your list. This is a throwaway meta-branch that is rebased often.
>
> The 'master' branch of libata-dev.git always contains the base commit
> from torvalds/linux-2.6.git from which all other branches are based. I
> never ever commit to the 'master' branch, only update it from
> torvalds/linux-2.6.git.
>
>
> Andrew,
>
> I will continue to maintain the 'ALL' branch exactly as before. It may
> contain changes not suitable for 'NEXT', but suitable for -mm testing.
>
> In my new development process, things will almost always land in 'ALL'
> before 'NEXT'.
So does this indicate the meaning of upstream and upstream-fixes is
still the same? I always took upstream-fixes to be bug fixes for this
-rc and upstream as queued for the next merge window, in which case NEXT
would be the union of those two sets?
James
next prev parent reply other threads:[~2008-02-14 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080215003537.8911ce35.sfr@canb.auug.org.au>
2008-02-14 21:03 ` linux-next: first tree Jeff Garzik
2008-02-14 21:05 ` Jeff Garzik
2008-02-14 21:26 ` James Bottomley [this message]
2008-02-14 21:45 ` Jeff Garzik
2008-02-14 23:58 ` Stephen Rothwell
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=1203024381.3158.26.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).