From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/6] tar: bump to version 1.28
Date: Tue, 14 Oct 2014 23:11:14 +0200 [thread overview]
Message-ID: <543D9172.7030700@mind.be> (raw)
In-Reply-To: <543D4035.5050308@zacarias.com.ar>
On 14/10/14 17:24, Gustavo Zacarias wrote:
> On 10/14/2014 11:52 AM, Peter Korsgaard wrote:
>
>> Please add S-O-B and note where it comes from exactly (upstream
>> presumably?)
>
> It's already upstream from the tar maintainer
> http://git.savannah.gnu.org/cgit/tar.git
> I tend not to touch the pristine ones that are already applied.
In that case, you should probably not add them to buildroot but instead do
TAR_PATCH = http://git.savannah.gnu.org/cgit/tar.git/patch/?id=e9ddc08da0982f36581ae5a8c7763453ff41cfe8
no?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-10-14 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 10:53 [Buildroot] [PATCH 1/6] radvd: bump to version 2.8 Gustavo Zacarias
2014-10-14 10:54 ` [Buildroot] [PATCH 2/6] gnutls: bump to version 3.2.19 Gustavo Zacarias
2014-10-14 10:54 ` [Buildroot] [PATCH 3/6] make: bump to version 4.1 Gustavo Zacarias
2014-10-14 10:54 ` [Buildroot] [PATCH 4/6] libcdio: bump to version 0.93 Gustavo Zacarias
2014-10-14 10:54 ` [Buildroot] [PATCH 5/6] libnss: bump to version 3.17.2 Gustavo Zacarias
2014-10-14 10:54 ` [Buildroot] [PATCH 6/6] tar: bump to version 1.28 Gustavo Zacarias
2014-10-14 14:52 ` Peter Korsgaard
2014-10-14 15:24 ` Gustavo Zacarias
2014-10-14 21:11 ` Arnout Vandecappelle [this message]
2014-10-19 13:38 ` Gustavo Zacarias
2014-10-14 14:52 ` [Buildroot] [PATCH 1/6] radvd: bump to version 2.8 Peter Korsgaard
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=543D9172.7030700@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.