public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Cc: furriner67@hotmail.com Subject: Re: FW: Cygwin start menu / mirrors Date: Thu, 02 Oct 2014 12:19:00 -0000 [thread overview] Message-ID: <542D42CE.6070602@dronecode.org.uk> (raw) In-Reply-To: <COL125-W36951BE4862EA821A997BACDB90@phx.gbl> Firstly, please do not send me personal email. Please read http://cygwin.com/problems.html#personal-email, particularly the section starting "Shouldn't I just send email to straight to a Cygwin developer or package maintainer?" On 02/10/2014 11:07, t s wrote: > Do these updates solve the problem with the start menu? No, they solve the problems that they say they solve. If you are uncertain, you could always test it yourself. > In addition to upstream fixes [1][2], this contains the following cygwin-specific changes since 1.16.0-2: > > * Also automatically activate the -nolock option if /tmp is on an exFAT filesystem (Reported by 't s') > * Log owning HWND when OpenClipboard fails > * Log name of format atom when conversion of X clipboard to a format is refused > * Also use _NET_WM_NAME for window titles in multiwindow mode > * Downgrade some uninformative, always-emitted log output to debug > * Check TEMP and TMP directories for accessibility before using for xkbcomp temporary file > * Log filename when xkbcomp temporary file cannot be opened > * Don't add an extra null character at the end of the text on the Windows clipboard (Thanks to Colin Harrison for patch) -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
prev parent reply other threads:[~2014-10-02 12:19 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <COL125-W45E02D0FF814E98332ADDDCDB90@phx.gbl> 2014-10-02 10:07 ` t s 2014-10-02 11:41 ` Marco Atzeri 2014-10-02 12:19 ` Jon TURNEY [this message]
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=542D42CE.6070602@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=furriner67@hotmail.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).