Linux backports project
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	backports@vger.kernel.org
Subject: Re: newbie questions
Date: Mon, 31 Aug 2015 15:33:32 +0200	[thread overview]
Message-ID: <1441028012.13980.10.camel@sipsolutions.net> (raw)
In-Reply-To: <55E454C9.5070302@linux.intel.com>

On Mon, 2015-08-31 at 08:21 -0500, Pierre-Louis Bossart wrote:
> > 
> > The *to* version is never relevant. A given backport will compile
> > against many different *to* versions.
> 
> I guess I completely missed the concept. I was thinking that the 
> gentree.py command would only port and adjust the delta between linux
> -next and the version I wanted. Looks like the backport is really an 
> add-on that will apply to multiple versions. Not sure I understand 
> how successive changes in the tree are handled if there is a single 
> backport.

Well, there's a single *from* version, as you say that was currently
"next-20150731" (or that was the one you used). The backport git
repository is maintained in lockstep with the *from* version (although
there's usually quite a bit of wiggle room)

The result, the output of backports, will/should compile against any
kernel starting from the earliest supported, all the way up to the
*from* version, right now I think that's 3.0 until 4.1 or so.

johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

  reply	other threads:[~2015-08-31 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  0:30 newbie questions Pierre-Louis Bossart
2015-08-31  7:43 ` Johannes Berg
2015-08-31 12:50   ` Pierre-Louis Bossart
2015-08-31 12:54     ` Johannes Berg
2015-08-31 13:21       ` Pierre-Louis Bossart
2015-08-31 13:33         ` Johannes Berg [this message]
2015-08-31 14:26           ` Pierre-Louis Bossart
2015-08-31 14:38             ` Johannes Berg

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=1441028012.13980.10.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=backports@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.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