From: Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: Andreas Jaeger <aj@suse.com>,
GNU C Library <libc-alpha@sourceware.org>,
libc-ports@sourceware.org
Subject: Re: [all-arch-ping][BZ #15465] Avoid crashing with LD_DEBUG=symbols when program name is unavailable
Date: Wed, 29 May 2013 16:06:00 -0000 [thread overview]
Message-ID: <CAAHN_R2c8LbA_7rWK6vnBrJGxdfj-1qMyZfHfZm-y0E8L2RoRg@mail.gmail.com> (raw)
In-Reply-To: <51A57DB5.1040104@redhat.com>
On 29 May 2013 09:31, Carlos O'Donell <carlos@redhat.com> wrote:
> Given that this is a mechanical cleanup of the machines
> it seems OK to me to check it in without getting approval
> from all the machine maintainers.
Thanks, I've checked this in.
Siddhesh
--
http://siddhesh.in
prev parent reply other threads:[~2013-05-29 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 10:29 [PATCH][BZ " Siddhesh Poyarekar
2013-05-14 13:35 ` Andreas Jaeger
2013-05-21 7:16 ` [all-arch-ping][BZ " Siddhesh Poyarekar
2013-05-29 4:02 ` Carlos O'Donell
2013-05-29 16:06 ` Siddhesh Poyarekar [this message]
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=CAAHN_R2c8LbA_7rWK6vnBrJGxdfj-1qMyZfHfZm-y0E8L2RoRg@mail.gmail.com \
--to=siddhesh.poyarekar@gmail.com \
--cc=aj@suse.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
/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).