From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: eggert@cs.ucla.edu, ravi@ravidesai.com, emacs-devel@gnu.org
Subject: Re: EMACS_INT to EMACS_UINT
Date: Mon, 05 Dec 2016 20:38:36 +0200 [thread overview]
Message-ID: <83mvgajk5v.fsf@gnu.org> (raw)
In-Reply-To: <866bb879-1089-7b1a-d483-0ca436cfcf29@dancol.org> (message from Daniel Colascione on Mon, 5 Dec 2016 09:47:34 -0800)
> From: Daniel Colascione <dancol@dancol.org>
> Date: Mon, 5 Dec 2016 09:47:34 -0800
> Cc: emacs-devel@gnu.org
>
> The GDB people are slowly migrating their C-style codebase to C++
Not slowly at all, watch gdb-patches.
prev parent reply other threads:[~2016-12-05 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 23:16 EMACS_INT to EMACS_UINT Ravi Desai
2016-12-05 2:00 ` Paul Eggert
2016-12-05 13:56 ` Ravi Desai
2016-12-05 17:23 ` Paul Eggert
2016-12-05 17:47 ` Daniel Colascione
2016-12-05 18:38 ` Eli Zaretskii [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
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=83mvgajk5v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dancol@dancol.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=ravi@ravidesai.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.
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).