From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: bug in procps-ng
Date: Fri, 15 Mar 2019 16:05:00 -0000 [thread overview]
Message-ID: <87va0k5dik.fsf@Rainer.invalid> (raw)
In-Reply-To: <20190315115221.GO3785@calimero.vinschen.de> (Corinna Vinschen's message of "Fri, 15 Mar 2019 12:52:21 +0100")
Corinna Vinschen writes:
> - We can keep the code as is, or change that to Linux-compat, whatever
> you think is the right thing for procps-ng.
Either way is fine for procps-ng, since in both cases there will need to
be some Cygwin specific parts.
> - Whatever you decide, the result will go into the next Cygwin version.
OK, then I propose to leave things as they are. If anybody finds some
other application that presents a compelling reason for following Linux
more closely we can still change it then.
> - When I release the next Cygwin version, you update procps-ng and
> there won't be any reason to be backward compat.
No change, no requirement for a synchronized release. :-)
> Ideally: Decide today, and Cygwin 3.0.4 will be ready and released this
> weekend.
Great! I'll need to check if I can move my patches into the the
configury where they properly belong quickly enough, otherwise I'll
upload as soon I get the upload rights.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
next prev parent reply other threads:[~2019-03-15 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 17:03 Corinna Vinschen
2019-03-13 4:55 ` Brian Inglis
2019-03-13 10:28 ` Corinna Vinschen
2019-03-13 18:14 ` Achim Gratz
2019-03-14 20:25 ` Achim Gratz
2019-03-15 11:52 ` Corinna Vinschen
2019-03-15 16:05 ` Achim Gratz [this message]
2019-03-15 20:42 ` 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=87va0k5dik.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).