From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [patch] Support binary (0b...) numbers
Date: Mon, 11 Jan 2010 19:25:00 -0000 [thread overview]
Message-ID: <83d41g8mur.fsf@gnu.org> (raw)
In-Reply-To: <20100111181122.GC20336@host0.dyn.jankratochvil.net>
> Date: Mon, 11 Jan 2010 19:11:22 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org
>
> That makes sense. OK to check-in?
>
>
> Thanks,
> Jan
>
>
> 2010-01-11 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * NEWS: Document 0b binary number prefix parsing.
Yes, thanks.
next prev parent reply other threads:[~2010-01-11 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 14:38 Jan Kratochvil
2010-01-11 15:03 ` Tristan Gingold
2010-01-11 18:01 ` Jan Kratochvil
2010-01-11 17:51 ` Tom Tromey
2010-01-11 17:59 ` Jan Kratochvil
2010-01-11 17:57 ` Joel Brobecker
2010-01-11 18:12 ` Jan Kratochvil
2010-01-11 19:25 ` Eli Zaretskii [this message]
2010-01-11 19:31 ` Jan Kratochvil
2010-01-11 19:06 ` Michael Snyder
2010-01-11 23:03 ` Mark Kettenis
2010-01-12 1:09 ` Stan Shebs
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=83d41g8mur.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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