From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: Keep calm
Date: Wed, 16 Mar 2016 18:30:00 -0000 [thread overview]
Message-ID: <56E9A61E.4060005@dronecode.org.uk> (raw)
In-Reply-To: <87h9g6disy.fsf@Rainer.invalid>
On 16/03/2016 06:43, Achim Gratz wrote:
> Jon Turney writes:
>> I've disabled upset (the perl script on sourceware.org, which performs
>> the task of composing setup.ini from setup.hints and moving uploads),
>> and enabled calm (a re-write from scratch to perform these tasks).
>
> The access rights on the setup.ini file are borked. Can you please fix
> them?
This was fixed by sourceware pixies. I've updated the script to avoid a
re-occurrence.
> Also, it would be really cool if setup.xz files were finally made
> available (the best compression option in my experience is -6e).
This is something I want to look at, once the initial problems have been
sorted out.
next prev parent reply other threads:[~2016-03-16 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 22:35 Jon Turney
2016-03-16 6:43 ` Achim Gratz
2016-03-16 18:30 ` Jon Turney [this message]
2016-03-29 18:19 ` Jon Turney
2016-04-01 19:10 ` Achim Gratz
2016-03-16 23:51 ` Yaakov Selkowitz
2016-03-17 7:53 ` [PLUSH HIPPO and GOLDSTAR] " Corinna Vinschen
2016-03-17 13:46 ` Andrew Schulman
2016-03-17 14:05 ` Corinna Vinschen
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=56E9A61E.4060005@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@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).