From: gmate.amit@gmail.com (Kumar amit mehta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Managing linux-next tree for submitting patches
Date: Wed, 21 Nov 2012 14:06:10 +0530 [thread overview]
Message-ID: <20121121083610.GE2743@gmail.com> (raw)
In-Reply-To: <CAHdPZaPoSQVXOFmcxp9YOmdRqyv1=GZMdEX4fyOKmSCpFPXZ-A@mail.gmail.com>
On Wed, Nov 21, 2012 at 02:47:15AM -0500, devendra.aaru wrote:
> that maintainer's tree is next tree so that next can pickup. once the
> next pics up your changes gets merged there in next.
>
> always its good to work against' maintainers trees, if its a fix then
> its better work on the maintainer's torvalds's tree otherwise the next
> tree in maintainer's repo
In past, I've been advised to base my work against linux-next tree.
See the mail [1] from Greg K H.
[1] http://www.spinics.net/lists/newbies/msg46076.html
next prev parent reply other threads:[~2012-11-21 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 5:36 Managing linux-next tree for submitting patches Kumar amit mehta
2012-11-21 5:52 ` devendra.aaru
2012-11-21 6:43 ` Kumar amit mehta
2012-11-21 6:51 ` devendra.aaru
2012-11-21 7:01 ` Kumar amit mehta
2012-11-21 7:47 ` devendra.aaru
2012-11-21 8:36 ` Kumar amit mehta [this message]
2012-11-21 13:44 ` Greg Freemyer
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=20121121083610.GE2743@gmail.com \
--to=gmate.amit@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.