All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/6] tar: bump to version 1.28
Date: Sun, 19 Oct 2014 10:38:35 -0300	[thread overview]
Message-ID: <5443BEDB.4060603@zacarias.com.ar> (raw)
In-Reply-To: <543D9172.7030700@mind.be>

On 10/14/2014 06:11 PM, Arnout Vandecappelle wrote:

>  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?

That leads to particularly odd filenames on disk:
?id=e9ddc08da0982f36581ae5a8c7763453ff41cfe8
There's no inherent problem with that but looks pretty stray-y to me (no
package name identification).
It's also not the usual way.
I'll adjust the in-tree patch instead.
Regards.

  reply	other threads:[~2014-10-19 13:38 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
2014-10-19 13:38         ` Gustavo Zacarias [this message]
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=5443BEDB.4060603@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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.