public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Laurens Blankers <laurens@blankersfamily.com>
To: cygwin-xfree@cygwin.com
Subject: Re: xinit-1.3.4-1: breaking backwards compatibility
Date: Tue, 30 Dec 2014 16:07:00 -0000 [thread overview]
Message-ID: <54A2CDA3.6030502@blankersfamily.com> (raw)
In-Reply-To: <54A2CD0E.4080904@alice.it>
On 30-12-2014 17:04, Angelo Graziosi wrote:
> The same you can do with the link created as suggested in my previous
> replay.
You are probably right, but again, that is not the issue. The point I am
trying to make is that breaking configurations which have worked for
many years in a patch release is very bad practice.
Laurens
--
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:[~2014-12-30 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 16:04 Angelo Graziosi
2014-12-30 16:07 ` Laurens Blankers [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-30 12:46 Angelo Graziosi
2014-12-30 13:42 ` Laurens Blankers
2014-12-30 11:07 Laurens Blankers
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=54A2CDA3.6030502@blankersfamily.com \
--to=laurens@blankersfamily.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: 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).