Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
	       "'Doug Evans'" <dje@google.com>,
	"'Pedro Alves'" <alves.ped@gmail.com>,
	       gdb-patches@sourceware.org
Subject: Re: ARI troubles
Date: Mon, 30 Apr 2012 17:26:00 -0000	[thread overview]
Message-ID: <20120430171903.GA25793@host2.jankratochvil.net> (raw)
In-Reply-To: <20120426161545.GO10958@adacore.com>

On Thu, 26 Apr 2012 18:15:45 +0200, Joel Brobecker wrote:
> > Thus a discrete sub-directory would seem more natural to me.
> 
> I do not have a strong opinion on this. Any location is really
> fine with me.

I am fine with gdb/ but it should be checked in somewhere where it can be
modified, I even wrote
	[ARI patch] Verify cross-arch .S testsuite files compatibility
	http://sourceware.org/ml/gdb-patches/2012-03/msg00511.html

and I still have to do what the patch does by hand
	Re: Crash regression for gdb.ada/*.exp [Re: [RFA 2/3] Initial Fission support, rewrite DIE reading]
	http://sourceware.org/ml/gdb-patches/2012-04/msg01079.html


Thanks,
Jan


  reply	other threads:[~2012-04-30 17:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4f972bf9.44d8b60a.1aeb.73dcSMTPIN_ADDED@mx.google.com>
2012-04-25  1:06 ` Pedro Alves
2012-04-25 16:11   ` Joel Brobecker
2012-04-25 16:14     ` Pierre Muller
     [not found]     ` <4f98223f.094ab60a.6b23.1692SMTPIN_ADDED@mx.google.com>
2012-04-25 16:56       ` Doug Evans
2012-04-25 17:02         ` Joel Brobecker
2012-04-26 15:43           ` Doug Evans
2012-04-26 16:02             ` Pierre Muller
2012-04-26 16:31               ` Joel Brobecker
2012-04-30 17:26                 ` Jan Kratochvil [this message]
2012-04-24 23:00 Pierre Muller

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=20120430171903.GA25793@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=alves.ped@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=dje@google.com \
    --cc=gdb-patches@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