From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] network-manager: bump version to 1.2.0
Date: Fri, 29 Apr 2016 20:45:36 +0200 [thread overview]
Message-ID: <20160429184534.GA311@x230> (raw)
In-Reply-To: <877ffhy6ah.fsf@dell.be.48ers.dk>
> > Dear Vincent, Peter and Gustavo,
> > do you thing it's still relevant to keep the patch I added, which fixes build error
> > kernels headers < 3.17?
> If it is still needed then I think we should keep it around - 3.17 isn't
> that old. Didn't the patch get submitted upstream?
I don't think so (but I thought it had when I sent patch to buildroot).
I search whole NetworkManager's git and it's not there.
It was created by Lubomir Rintel
https://mail.gnome.org/archives/networkmanager-list/2015-July/msg00028.html, last
mention is here
https://mail.gnome.org/archives/networkmanager-list/2015-July/msg00033.html.
Kind regards,
Petr
prev parent reply other threads:[~2016-04-29 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 11:05 [Buildroot] [PATCH] network-manager: bump version to 1.2.0 Vicente Olivert Riera
2016-04-22 14:04 ` Gustavo Zacarias
2016-04-25 21:00 ` Peter Korsgaard
2016-04-26 8:29 ` Vicente Olivert Riera
2016-04-28 17:03 ` Petr Vorel
2016-04-28 17:47 ` Peter Korsgaard
2016-04-29 18:45 ` Petr Vorel [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=20160429184534.GA311@x230 \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/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