From: Johannes Berg <johannes@sipsolutions.net>
To: 吳重毅 <uranus0206@gmail.com>, backports@vger.kernel.org
Subject: Re: Question of backports
Date: Wed, 29 Mar 2017 10:52:12 +0200 [thread overview]
Message-ID: <1490777532.7948.15.camel@sipsolutions.net> (raw)
In-Reply-To: <CAN+BLYH=tkxSxJSv995+n83Zon0kqweNb6X8nWeKuLFtCepSmQ@mail.gmail.com> (sfid-20170324_113721_904132_74122683)
On Fri, 2017-03-24 at 18:36 +0800, 吳重毅 wrote:
> Hi:
> I am confuse with backports' parameter. First i found the mail list
> of
> http://lists.infradead.org/pipermail/ath10k/2017-March/009458.html
> And i follow the attachment to patch backports' git.
> I am success full create the backports-output, but some parameters
> confused me.
> The parameter "--git-revision next-20170310". Is it says i am using
> tag next-20170310 of source linux-next?
> Currently my git of backports is point at master.
> When i use the command in maillist to generate backport-output.
> What target of kernel version am i going to backport to ?
> kernel of tag next-20170310(linux-next) to which kernel version?
> If my backports git is point at tag v4.4.2 and --git-version is point
> at v4.11. Can i say i am backporting from 4.11 to 4.4.2?
--git-revision is for the kernel source you want to use.
backports has its own tagging/branching, intended to match the *source*
kernel.
the *target* kernel, the one you compile against, shouldn't matter at
all and support (roughly) 3.0-current.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2017-03-29 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 10:36 Question of backports 吳重毅
2017-03-29 8:52 ` Johannes Berg [this message]
2017-03-29 9:10 ` 吳重毅
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=1490777532.7948.15.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=uranus0206@gmail.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 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.