From: Steve deRosier <derosier@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: wpdster@gmail.com, backports@vger.kernel.org
Subject: Re: How to use backports?
Date: Tue, 15 May 2018 15:19:22 -0700 [thread overview]
Message-ID: <CALLGbRL915L0uTyJnhD7eQFy2aBgQzRQMW_XiLgfypmbW-sHvw@mail.gmail.com> (raw)
In-Reply-To: <1526416237.4450.17.camel@sipsolutions.net>
On Tue, May 15, 2018 at 1:31 PM Johannes Berg <johannes@sipsolutions.net>
wrote:
> > If folks don't tend to use this tool on Ubuntu LTS releases, what
> > version of Linux do you use it on? What is known to work?
> I usually use one of Debian/testing or Fedora (currently F27 while I
> wait for some things I can't upgrade).
> We do run it one some kind of Ubuntu LTS at work, but I suspect they
> also installed spatch by hand, no idea how though.
I usually run Ubuntu LTS (server, not desktop) for most of my Linux build
systems. Like Johannes mentioned, I build coccinelle from source. While
I'm aware of the >= 1.0.6 patch that went in a few days ago, I haven't
built with anything that modern yet. Fact is, since changing jobs recently,
I'm not using backports as much as I used to since I'm stuck working on a
vendor driver.
Anyway, sorry I'm not that much help - I just wanted to answer your "does
anyone use Ubuntu for backports building" question. Answer is yes, it's
possible to do so.
- Steve
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2018-05-15 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 19:41 How to use backports? Patrick Doyle
2018-05-15 20:04 ` Johannes Berg
2018-05-15 20:26 ` Patrick Doyle
2018-05-15 20:30 ` Johannes Berg
2018-05-15 22:19 ` Steve deRosier [this message]
2018-05-16 13:24 ` Patrick Doyle
2018-05-16 13:26 ` Johannes Berg
2018-05-16 13:28 ` Patrick Doyle
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=CALLGbRL915L0uTyJnhD7eQFy2aBgQzRQMW_XiLgfypmbW-sHvw@mail.gmail.com \
--to=derosier@gmail.com \
--cc=backports@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=wpdster@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).