From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python-getdevinfo
Date: Sun, 13 Sep 2020 08:13:23 +0200 [thread overview]
Message-ID: <87o8ma19x8.fsf@Rainer.invalid> (raw)
In-Reply-To: <DB7PR02MB39966096B147B0C3DE78F70FE7250@DB7PR02MB3996.eurprd02.prod.outlook.com> (Hamish McIntyre-Bhatty via Cygwin-apps's message of "Sat, 12 Sep 2020 23:19:28 +0100")
Hamish McIntyre-Bhatty via Cygwin-apps writes:
> Hmm, who decides (and how) what counts as a Linux distro?
Something that is capable of and has actually done a license review.
> Either way, could anyone provide some insight as to whether bundling the
> Cygwin DLL would allow Cygwin programs to access the virtual /dev and
> /cygdrive paths? I have this all ready to be released for Windows, so
> one way or another I'll need to make a bundle anyway for convenience.
Yes, all the virtual fs are provided through the Cygwin DLL.
> It'd be great if it could make it into the official repos but I first
> submitted this ITP around a month ago so I don't have high hopes as of
> this point.
You still haven't explained what it would be useful for. This
bare-metal stuff isn't something I'd usually consider doing from within
a userland compatibility layer running on Windows.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2020-09-13 6:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 13:33 Hamish McIntyre-Bhatty
2020-08-17 13:34 ` Hamish McIntyre-Bhatty
2020-08-19 5:53 ` Marco Atzeri
2020-08-19 11:22 ` Hamish McIntyre-Bhatty
2020-08-20 6:01 ` Marco Atzeri
2020-08-21 15:33 ` Hamish McIntyre-Bhatty
2020-08-26 9:35 ` Hamish McIntyre-Bhatty
2020-09-02 15:29 ` Hamish McIntyre-Bhatty
2020-09-02 18:05 ` Marco Atzeri
2020-09-02 20:58 ` Hamish McIntyre-Bhatty
2020-09-03 13:44 ` marco atzeri
2020-09-03 14:10 ` Hamish McIntyre-Bhatty
2020-09-03 16:34 ` Ken Brown
2020-09-03 17:13 ` Hamish McIntyre-Bhatty
2020-09-03 17:27 ` Hamish McIntyre-Bhatty
2020-09-03 18:50 ` Ken Brown
2020-09-04 13:38 ` Hamish McIntyre-Bhatty
2020-09-09 10:36 ` Hamish McIntyre-Bhatty
2020-09-12 22:19 ` Hamish McIntyre-Bhatty
2020-09-13 6:13 ` Achim Gratz [this message]
2020-09-13 7:39 ` Hamish McIntyre-Bhatty
2020-09-13 15:02 ` Brian Inglis
2020-09-13 16:08 ` Hamish McIntyre-Bhatty
2020-09-14 18:29 ` Hamish McIntyre-Bhatty
2020-09-13 14:57 ` Jon Turney
2020-09-13 16:07 ` Hamish McIntyre-Bhatty
2020-09-22 13:32 ` Hamish McIntyre-Bhatty
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=87o8ma19x8.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).