From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] vpnc: bump to newer upstream version
Date: Fri, 3 Jun 2016 16:14:05 +0200 [thread overview]
Message-ID: <20160603161405.0b2ba998@free-electrons.com> (raw)
In-Reply-To: <20160419221637.GK3505@free.fr>
Hello,
On Wed, 20 Apr 2016 00:16:37 +0200, Yann E. MORIN wrote:
> > +Submitted upstream at https://github.com/ndpgroup/vpnc/pull/6
>
> There has been a comment to request the patches be mailed to the "real"
> upstream, and the PR was closed.
I submitted upstream:
http://lists.unix-ag.uni-kl.de/pipermail/vpnc-devel/2016-June/004186.html.
> > depends on BR2_USE_MMU # fork()
> > + depends on BR2_USE_WCHAR
>
> Is it because of gnutls, or does vpnc requires it for itself?
> If the former, you forgot the associated comment:
Because of gnutls, so I've added the comment.
> > +commit "vpnc needs a toolchain w/ wchar"
>
> Nope, this is not a commit; this is a comment. ;-)
Fixed. I've applied with those changes.
Thanks for the review!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-06-03 14:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 23:03 [Buildroot] [PATCH 0/4] vpnc: update and fix musl build Thomas Petazzoni
2016-02-10 23:03 ` [Buildroot] [PATCH 1/4] vpnc: switch to github as the new site Thomas Petazzoni
2016-04-19 22:04 ` Yann E. MORIN
2016-04-20 21:12 ` Thomas Petazzoni
2016-02-10 23:03 ` [Buildroot] [PATCH 2/4] vpnc: simplify patch 0001 Thomas Petazzoni
2016-04-19 22:05 ` Yann E. MORIN
2016-04-20 21:12 ` Thomas Petazzoni
2016-02-10 23:03 ` [Buildroot] [PATCH 3/4] vpnc: bump to newer upstream version Thomas Petazzoni
2016-04-19 22:16 ` Yann E. MORIN
2016-06-03 14:14 ` Thomas Petazzoni [this message]
2016-02-10 23:03 ` [Buildroot] [PATCH 4/4] vpnc: add patches to fix build with the musl C library Thomas Petazzoni
2016-06-03 14:14 ` Thomas Petazzoni
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=20160603161405.0b2ba998@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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