public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com> To: cygwin-xfree@cygwin.com Subject: Re: run.exe will not work with upgrade from 1.14.4 to 1.16.3 Date: Mon, 05 Jan 2015 10:34:00 -0000 [thread overview] Message-ID: <54AA68A2.2080808@cygwin.com> (raw) In-Reply-To: <54AA617B.6050105@blankersfamily.com> On 2015-01-05 04:03, Laurens Blankers wrote: > On 5-1-2015 10:48, Yaakov Selkowitz wrote: >> Just .startxwinrc, and the changes were explained in the announcement. > The information is contained within the announcement, but it is a bit > difficult to figure out what to do from just the list of changes. A more > detailed step-by-step guide, preferably as part of the FAQ would be very > much appreciated. I can't be everyone's personal IT department. I believe the information in the announcement contains sufficient information for users to make the necessary changes, but the most important part would be the new requirements of ~/.startxwinrc. >> ssh -X hasn't been supported since X11R7.4 way back in 2008 (see the >> FAQ for details). > I see, but PuTTY which apparently uses insecure forwards has worked for > many years all the way up to 1.3.2-1. Then please provide complete details in a separate thread. >> I am not going to revert the recent changes, which are important and >> long overdue. If any has constructive suggestions for incremental >> improvements thereto, they will be duly considered, but going >> backwards is not the solution. > OK, I am a bit disappointed, but I do have some suggestions. How would > you prefer I post them? In this thread or a new one? All together or one > post per suggestion? Please start a new thread. >> That won't be necessary. As a rolling distribution without stable >> releases, these kind of changes in UX happen from time to time. >> That's what announcements are for. > Are you saying it is inappropriate to discuss or that you personally > don't see value in this? There is simply no point. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2015-01-05 10:34 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-02 20:11 schilpfamily 2015-01-02 20:21 ` Laurens Blankers 2015-01-02 20:35 ` schilpfamily 2015-01-03 3:49 ` Larry Hall (Cygwin-X) 2015-01-03 8:04 ` Laurens Blankers 2015-01-03 9:25 ` rcunningham 2015-01-03 23:02 ` Larry Hall (Cygwin-X) 2015-01-04 11:41 ` Laurens Blankers 2015-01-05 4:04 ` Larry Hall (Cygwin-X) 2015-01-05 9:07 ` Laurens Blankers 2015-01-05 9:49 ` Yaakov Selkowitz 2015-01-05 10:03 ` Laurens Blankers 2015-01-05 10:34 ` Yaakov Selkowitz [this message] 2015-01-06 4:19 ` Larry Hall (Cygwin-X) 2015-01-12 0:26 ` solution for package startup scripts changing: do your own (was Re: run.exe will not work with upgrade from 1.14.4 to 1.16.3) Linda Walsh
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=54AA68A2.2080808@cygwin.com \ --to=yselkowitz@cygwin.com \ --cc=cygwin-xfree@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: linkBe 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).