public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: "'Joel Brobecker'" <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: run the ARI on gdbserver too?
Date: Fri, 16 Nov 2012 16:14:00 -0000	[thread overview]
Message-ID: <50A66666.1030003@redhat.com> (raw)
In-Reply-To: <005501cdc413$d3a808c0$7af81a40$@muller@ics-cnrs.unistra.fr>

On 16-11-2012 16:02, Pierre Muller wrote:

>   I was wondering if I could
> commit as obvious ARI fixes to gdbserver 
> directory, so that, when we finally add
> gdbserver to the ARI directory list
> (in fact remove the line pruning the directory in contrib./ari/gdb_find.sh
> script)
> we would get a lower increase of the number of problems...

The obvious rule as described in MAINTAINERS also applies to gdbserver.
There's no particular "ARI fixes are obvious" golden rule.  If any given
individual change is obvious, then go right ahead and check it in.  If not,
post first.

Thanks.

-- 
Pedro Alves

  reply	other threads:[~2012-11-16 16:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12  9:37 New ARI web page, generated using script inside CVS tree in gdb/contrib/ari directory Pierre Muller
2012-11-12 18:07 ` Joel Brobecker
2012-11-12 18:28   ` Pedro Alves
2012-11-12 18:38     ` Joel Brobecker
2012-11-12 18:48       ` Pedro Alves
2012-11-12 18:52         ` Joel Brobecker
2012-11-12 18:38   ` run the ARI on gdbserver too? Pedro Alves
2012-11-13 10:01     ` Pierre Muller
2012-11-16 16:03     ` Pierre Muller
2012-11-16 16:14       ` Pedro Alves [this message]
2012-11-14 16:41   ` New ARI web page, generated using script inside CVS tree in gdb/contrib/ari directory Tom Tromey
2012-11-14 16:59     ` Joel Brobecker

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=50A66666.1030003@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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).