From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] fs/tar: support passing long options to tar
Date: Sat, 25 Jun 2016 15:42:57 +0200 [thread overview]
Message-ID: <20160625154257.40e8a952@free-electrons.com> (raw)
In-Reply-To: <1466783876-7597-1-git-send-email-fhunleth@troodon-software.com>
Hello,
On Fri, 24 Jun 2016 11:57:56 -0400, Frank Hunleth wrote:
> Move TAR_OPTS so that long options (or any option with an initial '-')
> may be passed to tar. Since TAR_OPTS is at the front of the list, single
> letter options still work.
>
> Signed-off-by: Frank Hunleth <fhunleth@troodon-software.com>
> ---
> Changes v1 -> v2:
> - Move TAR_OPTS to front to preserve backward compatibility
> (suggested by Arnout)
> - Removed additional help text since no backward compatibility issues
> were introduced.
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-06-25 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 15:57 [Buildroot] [PATCH v2] fs/tar: support passing long options to tar Frank Hunleth
2016-06-25 13:42 ` Thomas Petazzoni [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=20160625154257.40e8a952@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 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.