From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Mark Wielaard <mjw@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] DWARFv5. Handle DW_TAG_atomic_type _Atomic type modifier.
Date: Mon, 23 Jun 2014 18:00:00 -0000 [thread overview]
Message-ID: <87egyf5wx5.fsf@fleche.redhat.com> (raw)
In-Reply-To: <53A86867.9000202@redhat.com> (Pedro Alves's message of "Mon, 23 Jun 2014 18:48:23 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> The best is to add a wiki page, and then add a pointer here:
Pedro> https://sourceware.org/gdb/wiki/OngoingWork
Yeah. And I think bugzilla works well for smaller things.
Tom
next prev parent reply other threads:[~2014-06-23 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 10:25 Mark Wielaard
2014-06-23 16:27 ` Tom Tromey
2014-06-23 17:07 ` Mark Wielaard
2014-06-23 17:48 ` Pedro Alves
2014-06-23 18:00 ` Tom Tromey [this message]
2014-06-23 18:01 ` Eric Christopher
2014-06-23 21:34 ` Mark Wielaard
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=87egyf5wx5.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mjw@redhat.com \
--cc=palves@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