From: Ken Brown <kbrown@cornell.edu>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: Make native clipboard layout same for 32- and 64-bit
Date: Sat, 23 Oct 2021 16:32:43 -0400 [thread overview]
Message-ID: <0cdc8601-fd90-226a-d486-7204bbe604c6@cornell.edu> (raw)
In-Reply-To: <12fea3e3-92ae-2a33-81ea-808bdcc20f2a@maxrnd.com>
On 10/23/2021 1:35 AM, Mark Geisert wrote:
> Corinna Vinschen wrote:
>> Just to close this up prior to the 3.3.0 release...
>>
>> Given we never actually strived for 32<->64 bit interoperability, it's
>> hard to argue why this should be different for the clipboard stuff.
>>
>> Running 32 and 64 bit Cygwin versions in parallel doesn't actually make
>> much sense for most people anyway, unless they explicitely develop for
>> 32 and 64 bit systems under Cygwin. From a productivity point of view
>> there's no good reason to run more than one arch.
>>
>> So I agree with Ken here. It's probably not worth the trouble.
>
> Sorry, I've been sidetracked for a bit. I can agree with Ken too. The only
> circumstance I could think of where multiple internal format support might be
> useful (to non-developers) was some user hanging on to an older Cygwin because
> it was needed to support something else (s/w or h/w) old and non-upgradeable.
> Doesn't seem very likely at this point.
>
> I'll try to get the v2 patch out over this weekend. Same end-result for same
> environments as the v1 patch, but incorporating all the comments I received.
I think Corinna was saying that the whole idea of making the 32-bit and 64-bit
clipboards interoperable is not worth the trouble.
> To that end, does Jon's suggestion of /usr/include/sys/cygwin.h seem like the
> best location to define struct cygcb_t for use by both Cygwin and cygutils package?
> Thanks much,
>
> ..mark
next prev parent reply other threads:[~2021-10-23 20:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 5:22 Mark Geisert
2021-10-07 5:56 ` Mark Geisert
2021-10-08 9:52 ` Takashi Yano
2021-10-09 14:19 ` Ken Brown
2021-10-09 14:29 ` Jon Turney
2021-10-09 14:43 ` Ken Brown
2021-10-11 6:13 ` Mark Geisert
2021-10-11 12:11 ` Ken Brown
2021-10-22 15:11 ` Corinna Vinschen
2021-10-23 5:35 ` Mark Geisert
2021-10-23 20:32 ` Ken Brown [this message]
2021-10-23 21:53 ` Mark Geisert
2021-10-23 23:58 ` Takashi Yano
2021-10-25 8:28 ` 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=0cdc8601-fd90-226a-d486-7204bbe604c6@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-patches@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).