From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Broken file in ALL cygwin mirrors report! socat-debuginfo
Date: Sat, 20 Oct 2018 17:07:00 -0000 [thread overview]
Message-ID: <87ftx0pmx0.fsf@Rainer.invalid> (raw)
In-Reply-To: <4485ee8acd5ce4977bf370345f6f6718@smtp-cloud9.xs4all.net> (Houder's message of "Sat, 20 Oct 2018 18:03:04 +0200")
Houder writes:
> The latter ones will properly untar, but not the files of size 32.
There is a special branch in setup that accepts this particular case for
historical reasons.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
--
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
prev parent reply other threads:[~2018-10-20 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 16:31 hno
2018-10-19 16:45 ` Marco Atzeri
2018-10-20 14:03 ` Andrew Schulman
2018-10-20 14:59 ` Marco Atzeri
2018-10-20 16:03 ` Houder
2018-10-20 16:58 ` Marco Atzeri
2018-10-20 17:07 ` Achim Gratz [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=87ftx0pmx0.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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).