From: Tom Tromey <tromey@redhat.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Emacs discussions <emacs-devel@gnu.org>
Subject: Re: baby step toward thread patch
Date: Wed, 19 Jan 2011 08:00:42 -0700 [thread overview]
Message-ID: <m339opgcpx.fsf@fleche.redhat.com> (raw)
In-Reply-To: <bdk4i1ff3b.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 19 Jan 2011 03:54:48 -0500")
>>>>> "GM" == Glenn Morris <rgm@gnu.org> writes:
GM> Something wrong in the following diff hunk?
GM> window.c:154:8: warning: extra tokens at end of #endif directive
Thanks. I am checking in a fix.
Just removing the stuff after the #endif is fine.
Tom
next prev parent reply other threads:[~2011-01-19 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 14:40 baby step toward thread patch Tom Tromey
2011-01-18 20:42 ` Tom Tromey
2011-01-19 8:27 ` Thien-Thi Nguyen
2011-01-19 8:54 ` Glenn Morris
2011-01-19 15:00 ` Tom Tromey [this message]
2011-01-20 15:41 ` Tom Tromey
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=m339opgcpx.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
/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).