Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [patch 2/2, 7.3] Fix 7.1->7.2 regression: info sources
Date: Fri, 10 Jun 2011 20:56:00 -0000	[thread overview]
Message-ID: <m3oc258kye.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110610203300.GB31746@host1.jankratochvil.net> (Jan	Kratochvil's message of "Fri, 10 Jun 2011 22:33:00 +0200")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> I believe it should go for 7.3, I will check it in there.

I agree.

Jan> 	* symtab.c (output_partial_symbol_filename): Exchange the filename and
Jan> 	fullname parameters order.

This isn't the first bug like this :-(

Tom


  reply	other threads:[~2011-06-10 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10 20:33 Jan Kratochvil
2011-06-10 20:56 ` Tom Tromey [this message]
2011-06-10 22:00   ` Jan Kratochvil
2011-06-10 21:26 ` 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=m3oc258kye.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --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