From: Vince Rice <vrice@solidrocksystems.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ATTN: Yaakov Selkowitz / PHP maintainer] Re: Composer segfault on multiple configurations
Date: Wed, 31 May 2017 01:02:00 -0000 [thread overview]
Message-ID: <0A1D1389-70EC-401A-A03B-029E9889EEDF@solidrocksystems.com> (raw)
In-Reply-To: <1787C54E-D0B7-4611-8D07-81E717A1F0AA@solidrocksystems.com>
>> On May 30, 2017, at 11:47 AM, Richard H Lee wrote:
>>
>> Yaakov,
>>
>> I probably should have copied you in on the last message to get your attention.
>>
>> It's just a simple patch to fix this page size issue with php on Cygwin. Would be grateful if you could review and possibly accept this patch, as it has been confirmed and does affect several people.
> On May 30, 2017, at 1:59 PM, Vince Rice <vrice@solidrocksystems.com> wrote:
>
> I'm sure he will tell you himself soon enough, but no you shouldn't have. Emails re packages should go to the list, not to the package maintainers directly. If you want to ping a previous message, ping the list, not the person.
And of course I realized too late I TOFU'd… Sorry about that.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-05-30 19:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 19:32 Sky Diver
2017-05-17 20:47 ` Richard H Lee
2017-05-18 11:02 ` Sky Diver
2017-05-18 12:35 ` Andrey Repin
2017-05-18 13:33 ` Richard H Lee
2017-05-18 14:32 ` Sky Diver
2017-05-19 19:26 ` [ATTN: Yaakov Selkowitz / PHP maintainer] " Richard H Lee
2017-05-30 18:59 ` Richard H Lee
2017-05-30 20:47 ` Vince Rice
2017-05-31 1:02 ` Vince Rice [this message]
2017-05-22 19:54 ` Richard H Lee
2017-05-25 7:56 ` Sky Diver
2017-05-25 21:21 ` Memcache/d (Orig: Re: Composer segfault on multiple configurations) Richard H Lee
2017-05-27 10:51 ` Sky Diver
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=0A1D1389-70EC-401A-A03B-029E9889EEDF@solidrocksystems.com \
--to=vrice@solidrocksystems.com \
--cc=cygwin@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).