From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Sergio Durigan <sdurigan@redhat.com>
Subject: [commit] [patch 2/2] Do not build libgdb.a by default
Date: Mon, 02 Jan 2012 02:32:00 -0000 [thread overview]
Message-ID: <20120102023138.GB15664@host2.jankratochvil.net> (raw)
In-Reply-To: <m37h1pdee4.fsf@fleche.redhat.com>
On Wed, 21 Dec 2011 18:26:59 +0100, Tom Tromey wrote:
> Thanks. This seems like a sensible compromise approach to me.
> I am in favor of it.
Checked in:
http://sourceware.org/ml/gdb-cvs/2012-01/msg00011.html
Thanks,
Jan
next prev parent reply other threads:[~2012-01-02 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 11:58 Jan Kratochvil
2011-12-21 13:12 ` Joel Brobecker
2011-12-21 14:01 ` Pierre Muller
2011-12-21 14:24 ` Joel Brobecker
2011-12-21 14:27 ` Pierre Muller
2011-12-21 19:18 ` Tom Tromey
2012-01-02 2:32 ` Jan Kratochvil [this message]
2012-01-02 13:40 ` Pedro Alves
2012-01-02 14:02 ` [patch] Put solib-target.o back to COMMON_OBS [Re: [patch 2/2] Do not build libgdb.a by default] Jan Kratochvil
2012-01-02 17:12 ` Pedro Alves
2012-01-02 17:19 ` Jan Kratochvil
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=20120102023138.GB15664@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sdurigan@redhat.com \
--cc=tromey@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