From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mario@lassnig.net, 9960@debbugs.gnu.org, cyd@gnu.org,
9772@debbugs.gnu.org, 10155@debbugs.gnu.org
Subject: bug#9960: bug#10155: OSX breakage
Date: Tue, 29 Nov 2011 10:22:19 -0800 [thread overview]
Message-ID: <4ED522DB.3080005@cs.ucla.edu> (raw)
In-Reply-To: <83k46i6dl5.fsf@gnu.org>
On 11/29/11 09:30, Eli Zaretskii wrote:
> I wonder if we could have a much smaller change that
> fixes just that single problem.
Yes we could, though it would involve more of the patch
than the part that you've identified, and it would involve
some other stuff done by hand. The simplest way to think
about it is, I expect, is that it would be a fork of gnulib.
I could look into preparing such a patch but it would take
some time and would introduce other reliability concerns,
so I hope I don't have to do that....
next prev parent reply other threads:[~2011-11-29 18:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ED3AA79.8060605@lassnig.net>
[not found] ` <838vn06swa.fsf@gnu.org>
[not found] ` <4ED3DA30.1050006@cs.ucla.edu>
[not found] ` <871usrh69t.fsf@gnu.org>
2011-11-29 9:28 ` bug#9772: OSX breakage Paul Eggert
2011-11-29 13:56 ` bug#9960: bug#10155: " Stefan Monnier
2011-11-29 16:58 ` Paul Eggert
2011-11-29 17:30 ` bug#9772: " Eli Zaretskii
2011-11-29 18:22 ` Paul Eggert [this message]
2011-11-30 2:45 ` bug#10155: " Chong Yidong
2011-11-30 4:04 ` Eli Zaretskii
2011-11-30 8:14 ` Chong Yidong
2011-11-30 11:15 ` bug#10155: " Mario Lassnig
2011-12-01 16:12 ` Paul Eggert
2011-11-30 17:48 ` bug#10155: " Jan Djärv
2011-11-29 16:39 ` bug#9772: " Eli Zaretskii
2011-11-30 2:27 ` Chong Yidong
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ED522DB.3080005@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=10155@debbugs.gnu.org \
--cc=9772@debbugs.gnu.org \
--cc=9960@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=eliz@gnu.org \
--cc=mario@lassnig.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).