[PATCH] Re: Cygwin select() issues and improvements
Thu May 19 00:02:00 GMT 2016
On 5/18/16 3:23 PM, Corinna Vinschen wrote:
> Hi John,
> On May 8 16:43, john hood wrote:
>> On 3/29/16 8:49 AM, Corinna Vinschen wrote:
>>> John, ping?
>> Sorry it took so long to reply, but I finally got around to cleaning up
>> the patchset, I've mailed it separately.
> I don't see the patchset anywhere. Did I miss your mail or did it
> fail to make it to this list?!?
It never made it to the list. Some aspect of my network's email config
(I still haven't figured out what) caused email sent directly by my
workstation to be dropped by the sourceware.org mail server. I changed
it to use my mail server instead and that worked.
>> I was pretty frustrated at my
>> slow Windows machine and the friction in dealing with the project,
> What friction? Was there anything I or others did to alienate you?
> If there's some problem, please also feel free to discuss on the
> #cygwin-developers IRC channel @Freenode. You're apparently lurking
The slow Windows machine is probably the larger part of that. It's a
netbook-class machine. It's very slow; development on it was rather
unpleasant. I just set up a VM with a Windows 10 preview on a fast
machine-- it's around four times faster.
But also, working with the email-and-patches style of work that you have
here is really considerably more work than working with projects on
GitHub (I'm a maintainer of a project there) or GitLab. The email
configuration issue above is a good example. It really is easier for
both contributors and maintainers. Assuming you have an account,
contributing a change is something like this: push a branch ("fork") to
the website's shared repo, go to its web view, enter your message for
the pull request, click send, and done. I know Cygwin/Redhat are
unlikely to move to GitHub, but GitLab offers the same basic workflow,
and I would guess 90% of the functionality of GitHub. I don't want to
over-emphasize this, but it is significant.
More information about the Cygwin-patches