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 13:18:12 +0200 [thread overview]
Message-ID: <87fsy53i17.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:
> Can you provide a commit id which triggers this which but shouldn't,
> and I'll try to work out why...
--8<---------------cut here---------------start------------->8---
[master 8c744db] protobuf: update to version 3.17.1
2 files changed, 22 insertions(+), 6 deletions(-)
Enumerating objects: 4, done.
Counting objects: 100% (4/4), done.
Delta compression using up to 8 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 1.29 KiB | 1.29 MiB/s, done.
Total 4 (delta 0), reused 0 (delta 0), pack-reused 0
remote: warning: 8c744dbfb212bf55bb5df60f3e63d337d40bd921 seems to contain more than one .cygport file
remote: this is bad and you should feel bad
--8<---------------cut here---------------end--------------->8---
No, there is only one cygport file and even if there were I would not and
should not feel bad.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2021-05-29 11:18 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
2021-05-29 11:18 ` Achim Gratz [this message]
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=87fsy53i17.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).