From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Andreas Arnez <arnez@linux.vnet.ibm.com>
Subject: Re: ping: [testsuite patch] for: [PATCH] [PR corefiles/17808] i386: Fix internal error when prstatus in core file is too big
Date: Tue, 17 Feb 2015 12:56:00 -0000 [thread overview]
Message-ID: <54E33A8D.80504@redhat.com> (raw)
In-Reply-To: <20150214151231.GA29106@host1.jankratochvil.net>
On 02/14/2015 03:12 PM, Jan Kratochvil wrote:
> On Thu, 05 Feb 2015 10:47:49 +0100, Pedro Alves wrote:
>> It's not obvious to me why is the file uuencoded. What's the
>> reason for that?
>
> I do not find it convenient to check in a binary, while GIT can handle that
> diff+patch do not.
>
> If you prefer a different encoding method I do not mind.
I'd rather just not uuencode the binary, dropping the dependency
on uudecode.
I think this is the first time we're adding a binary core dump
to the testsuite. I think elfutils (a GPLv3 project)
just puts test core binaries directly in git, right?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-02-17 12:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 16:16 Andreas Arnez
2015-01-08 16:43 ` [testsuite patch] for: " Jan Kratochvil
2015-01-09 9:47 ` Andreas Arnez
2015-01-09 16:45 ` Pedro Alves
2015-01-09 16:59 ` Mark Kettenis
2015-01-09 17:19 ` Pedro Alves
2015-01-09 19:35 ` Mark Kettenis
2015-01-09 20:11 ` Pedro Alves
2015-01-09 20:30 ` Mark Kettenis
2015-01-12 14:30 ` Andreas Arnez
2015-01-09 19:27 ` Andreas Arnez
2015-02-05 7:38 ` ping: " Jan Kratochvil
2015-02-05 9:47 ` Pedro Alves
2015-02-14 15:12 ` Jan Kratochvil
2015-02-17 12:56 ` Pedro Alves [this message]
2015-02-17 16:56 ` Jan Kratochvil
2015-02-21 14:28 ` [commit] " Jan Kratochvil
2015-07-14 8:52 ` ping: " Yao Qi
2015-07-14 18:07 ` Jan Kratochvil
2015-07-15 16:14 ` Yao Qi
2015-07-15 16:58 ` Jan Kratochvil
2015-07-16 14:15 ` Yao Qi
2015-07-16 14:37 ` Jan Kratochvil
2015-07-16 15:35 ` Yao Qi
2015-07-16 16:10 ` [commit] " 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=54E33A8D.80504@redhat.com \
--to=palves@redhat.com \
--cc=arnez@linux.vnet.ibm.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