From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [FYI v3 7/8] Add Rust documentation
Date: Tue, 17 May 2016 20:32:00 -0000 [thread overview]
Message-ID: <8360uc4eap.fsf@gnu.org> (raw)
In-Reply-To: <1463516288-26778-8-git-send-email-tom@tromey.com> (message from Tom Tromey on Tue, 17 May 2016 14:18:07 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>
> Date: Tue, 17 May 2016 14:18:07 -0600
>
> This patch adds documentation for the new Rust support in gdb.
>
> 2016-05-17 Tom Tromey <tom@tromey.com>
>
> * NEWS: Add Rust item.
>
> 2016-05-17 Tom Tromey <tom@tromey.com>
>
> * gdb.texinfo (Supported Languages): Mention Rust. Update menu.
> (Rust): New node.
I think I've already approved this part, haven't I?
Thanks.
next prev parent reply other threads:[~2016-05-17 20:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 20:18 [FYI v3 0/8] Add Rust language support Tom Tromey
2016-05-17 20:18 ` [FYI v3 1/8] Fix latent yacc-related bug in gdb/Makefile.in init.c rule Tom Tromey
2016-05-17 20:18 ` [FYI v3 3/8] Add self-test framework to gdb Tom Tromey
2016-05-17 20:32 ` Eli Zaretskii
2016-05-17 20:18 ` [FYI v3 7/8] Add Rust documentation Tom Tromey
2016-05-17 20:32 ` Eli Zaretskii [this message]
2016-05-17 20:18 ` [FYI v3 4/8] Add array start and end strings to generic_val_print_decorations Tom Tromey
2016-05-17 20:18 ` [FYI v3 8/8] Rename OP_F90_RANGE to OP_RANGE Tom Tromey
2016-05-18 2:31 ` Joel Brobecker
2016-05-17 20:18 ` [FYI v3 2/8] Make gdb expression debugging handle OP_F90_RANGE Tom Tromey
2016-05-17 20:19 ` [FYI v3 6/8] Update gdb test suite for Rust Tom Tromey
2016-05-17 20:19 ` [FYI v3 5/8] Add support for the Rust language Tom Tromey
2016-05-18 13:46 ` Ulrich Weigand
2016-05-18 16:17 ` Tom Tromey
2016-05-18 16:21 ` Ulrich Weigand
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=8360uc4eap.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).