From: Stephen Rothwell <sfr@canb.auug.org.au>
To: vibi_sreenivasan@cms.com
Cc: linux-next@vger.kernel.org
Subject: Re: On Which Branch I Have to Base Patches
Date: Tue, 2 Jun 2009 17:23:24 +1000 [thread overview]
Message-ID: <20090602172324.b32aecbc.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1243924710.2170.23.camel@system>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Hi,
On Tue, 02 Jun 2009 12:08:30 +0530 vibi sreenivasan <vibi_sreenivasan@cms.com> wrote:
>
> On which branch i have to base patches on
> linux-next/stable
This is just the place in Linus' tree that I started from for today's
version of linux-next (this only ever moves forward).
> linux-next/master
This is the complete linux-next tree for today (this is effectively
rebased every release).
> linux-next/history
This is just all the linux-next trees linked together (ignore this - it
is not a useful kernel tree).
> Where Can i get information on all these branches?
See above. Also see http://linux.f-seidel.de/linux-next/pmwiki/
To have a tree included in linux-next it must be based on a tree that is
not rebased (or if it does rebase you can guarantee that your tree is
rebased on top of it) that is included in linux-next already. In
practise this means "Linus' tree" unless you have dependencies on someone
else's tree.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-06-02 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 6:38 On Which Branch I Have to Base Patches vibi sreenivasan
2009-06-02 7:23 ` Stephen Rothwell [this message]
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=20090602172324.b32aecbc.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=vibi_sreenivasan@cms.com \
/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