public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: snapshots (archive files) are too big ... Why?
Date: Sun, 24 Jan 2016 01:22:00 -0000	[thread overview]
Message-ID: <878u3gxde8.fsf@Rainer.invalid> (raw)
In-Reply-To: <20160123181053.GF3268@calimero.vinschen.de> (Corinna Vinschen's	message of "Sat, 23 Jan 2016 19:10:53 +0100")

Corinna Vinschen writes:
> I found out why this happens, I just don't know why it only occurs since
> 2015-07-20.

Looks like this patch

http://pkgs.fedoraproject.org/cgit/rpms/tar.git/commit/?id=132f2c79628ff5f11bb7d41c5c34f94228d63c54

and the following two fixups would be a likely source of that change in
behaviour and it was probably the following package update that threw
the script off course.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
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:[~2016-01-23 20:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-23 14:35 Houder
2016-01-23 17:35 ` Andrey Repin
2016-01-23 18:10 ` Andrey Repin
2016-01-23 19:25   ` Houder
2016-01-23 20:13 ` Corinna Vinschen
2016-01-23 20:18   ` Houder
2016-01-23 21:56     ` Corinna Vinschen
2016-01-23 23:31       ` Houder
2016-01-24 10:12         ` Achim Gratz
2016-01-24 10:28           ` Houder
2016-01-24  1:22   ` Achim Gratz [this message]
2016-01-24 17:55     ` Corinna Vinschen
2016-01-24 18:36       ` Achim Gratz

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=878u3gxde8.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).