public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: problem with paste-from-clipboard
Date: Mon, 15 May 2017 20:00:00 -0000	[thread overview]
Message-ID: <cb873ea1-3546-7956-596a-ea4476cec667@redhat.com> (raw)
In-Reply-To: <5919e0cc.f3149d0a.5c156.0ea9@mx.google.com>


[-- Attachment #1.1: Type: text/plain, Size: 1788 bytes --]

On 05/15/2017 12:09 PM, Steven Penny wrote:
> On Sat, 13 May 2017 15:11:00, Eric Blake wrote:
>> You're making it sound like I'm actively trying to hurt you. Rather,
>> it's a case where it is a problem that doesn't affect me personally, and
>> I have limited enough spare time as it is, so I haven't yet tried to
>> reproduce things to see if I can isolate what behavior changed.
>>
>> I would love help solving the issue.  Absent that help, you'll just have
>> to wait for me to have time.
> 
> But I have helped - in the very post of mine you just quoted, I put this
> link:
> 
> http://cygwin.com/ml/cygwin/2017-04/msg00176.html
> 
> that post of mine contains not only the commit in question, but even
> potentially
> the file in question and even possibly the section of the file in
> question. You
> never even responded to that post.

Probably because I did not even see the post at the time. (While I try
to keep up with Cygwin email, I also get hundreds of other mails per
day, and when Cygwin is limited to my free time, sometimes things slip
through the cracks).  In life, and therefore in open source, it is often
that the squeaky wheel gets the grease; if something isn't getting the
attention you think it deserves, it is not bad to ping the thread to
bring it back to the forefront.

Thanks for the ping. I've now replied to that thread to ask upstream
bash for help in deciphering if Chet, who wrote the code, might be aware
of why it is breaking things.

That said, I still hope to get a closer look at it myself when I have a
nice chunk of time; but the trick is still getting that nice chunk of time.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2017-05-15 18:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 21:24 Ladislav DANKO
2017-05-13  2:50 ` Steven Penny
2017-05-13  7:38   ` Ladislav DANKO
2017-05-15 15:29   ` Eric Blake
2017-05-15 18:19     ` Steven Penny
2017-05-15 20:00       ` Eric Blake [this message]
2017-05-29 20:05         ` Ladislav DANKO
2017-09-01 14:03         ` Ladislav DANKO
2017-09-01 14:42           ` Eric Blake
2017-09-01 14:55             ` Ladislav DANKO
2017-09-01 15:24             ` Thomas Wolff
2017-09-01 16:00               ` Ladislav DANKO
2017-09-01 22:19             ` Steven Penny
2017-09-02  3:17               ` Brian Inglis
2018-08-07 19:31             ` Bosmon
2018-08-07 22:32               ` Steven Penny
2018-08-12  1:34                 ` Bosmon
2018-08-12  3:21                   ` Steven Penny
2018-08-13 19:02                     ` Bosmon
2018-08-14  3:37                       ` Steven Penny
2019-09-08 11:30                         ` Bosmon

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=cb873ea1-3546-7956-596a-ea4476cec667@redhat.com \
    --to=eblake@redhat.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).