From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] nghttp2, mingw64-{x86_64,i686}-nghttp2
Date: Sat, 29 May 2021 12:42:48 +0200 [thread overview]
Message-ID: <87o8ct3jo7.fsf@Rainer.invalid> (raw)
In-Reply-To: <c1aa73f3-51aa-4fd2-b9f1-d1fecb19c3c8@dronecode.org.uk> (Jon Turney's message of "Sat, 29 May 2021 11:09:06 +0100")
Jon Turney writes:
> This is a new trigger I turned on recently, which (is supposed to)
> prevent pushes of trees which contain more than one .cygport file
> (since that complicates navigating from source pacakage name to git
> history of the .cygport file in ways I have no interest in
> implementing)
Well, it was obvious that you didn't think it was useful, however I'd
really wish you would first discuss changes which prevent existing
practise to continue before implementing them. I was in the process of
preparing an RFC about the package repository structure since there are
obviously multiple ways of going about it, but I'm going to hold off for
now.
> I've tuned this down to a warning at the moment (and made it a bit
> clearer) so you should be able to proceed.
Thanks.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2021-05-29 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 17:06 Brian Inglis
2021-05-28 18:33 ` Marco Atzeri
2021-05-28 23:18 ` Brian Inglis
2021-05-29 4:37 ` Brian Inglis
2021-05-29 6:12 ` Marco Atzeri
2021-05-29 10:09 ` Jon Turney
2021-05-29 10:42 ` Achim Gratz [this message]
2021-05-29 11:18 ` Achim Gratz
2021-05-29 16:55 ` Brian Inglis
2021-05-29 18:01 ` Achim Gratz
2021-05-29 18:34 ` Brian Inglis
2021-05-29 16:18 ` Brian Inglis
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=87o8ct3jo7.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).