public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Steven Hartland" <killing@multiplay.co.uk>
To: "Aaron Schneider" <notstop@users.sourceforge.net>,	<cygwin@cygwin.com>
Subject: Re: tar won't extract all files when a file with exe extension precedes the same without extension inside the archive
Date: Thu, 12 Jul 2012 00:40:00 -0000	[thread overview]
Message-ID: <92B65842B4224F3FA65CE40F3608F7DF@multiplay.co.uk> (raw)
In-Reply-To: <BLU152-W148807FCA9B75410CB8F1FCED10@phx.gbl>

----- Original Message ----- 
From: "Aaron Schneider"
> $ touch myfile myfile.exe
>
> $ tar -cvf mytar.tar myfile.exe myfile
>
> $ tar -xvf mytar.tar
>
> Only myfile will be written to the filesystem

Yep, apparently its "by design" :(

It causes us pain regularly so we would like this fairly
recent change reverted so behaviour is once again predicatable
and it doesnt break simple takess like extracting archive.

    Regards
    Steve


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2012-07-12  0:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 20:51 Aaron Schneider
2012-07-11 21:03 ` marco atzeri
2012-07-12  0:40 ` Steven Hartland [this message]
2012-07-12  1:04   ` Christopher Faylor
2012-07-12  1:17     ` Steven Hartland
2012-07-12 12:05       ` Andrey Repin
2012-07-12 13:51         ` Larry Hall (Cygwin)
2012-07-12 16:26           ` Andy Hall
2012-07-12 16:42             ` Otto Meta
2012-07-12 17:09               ` Christopher Faylor
2012-07-13 16:20               ` Andy Hall
2012-07-13 17:26                 ` Christopher Faylor
2012-07-13 17:40                   ` Daniel Colascione
2012-07-13  1:05             ` Andrey Repin
2012-09-04 23:53 ` Steven Hartland
2012-09-05  6:18   ` Christopher Faylor

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=92B65842B4224F3FA65CE40F3608F7DF@multiplay.co.uk \
    --to=killing@multiplay.co.uk \
    --cc=cygwin@cygwin.com \
    --cc=notstop@users.sourceforge.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).