From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] network-manager: bump version to 1.2.0
Date: Thu, 28 Apr 2016 19:03:59 +0200 [thread overview]
Message-ID: <20160428170357.GB789@x230> (raw)
In-Reply-To: <571F26E5.2070300@imgtec.com>
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?
Kind regards,
Petr
next prev parent reply other threads:[~2016-04-28 17:03 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 [this message]
2016-04-28 17:47 ` Peter Korsgaard
2016-04-29 18:45 ` Petr Vorel
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=20160428170357.GB789@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