Hi Andrey,
while not being involved with this change, I may provide some background though:
On 2/6/19 1:36 AM, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
>> Changes from 3.0.0-0.3:
>
>> - Cygwin PIDs have been decoupled from Windows PID. Cygwin PIDs are
>> now incrementally dealt i
On Feb 6 03:36, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> > Changes from 3.0.0-0.3:
>
> > - Cygwin PIDs have been decoupled from Windows PID. Cygwin PIDs are
> > now incrementally dealt in the range from 2 up to 65535, POSIX-like.
>
> I don't quite get it.
> What's the rationale
Greetings, Corinna Vinschen!
> Changes from 3.0.0-0.3:
> - Cygwin PIDs have been decoupled from Windows PID. Cygwin PIDs are
> now incrementally dealt in the range from 2 up to 65535, POSIX-like.
I don't quite get it.
What's the rationale? Why not just use system PID's?
--
With best regard
Hi folks,
I uploaded a new Cygwin test release 3.0.0-0.4
This release comes with a couple of new features and some interesting
bug fixes.
It also changes the output of uname(2) for newly built applications.
Applications built so far (that includes uname(1) from coreutils)
will still print the o
4 matches
Mail list logo
