From: Roland McGrath <roland@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: elfutils import
Date: Wed, 22 Aug 2007 21:52:00 -0000 [thread overview]
Message-ID: <20070822215158.AFB804D0418@magilla.localdomain> (raw)
In-Reply-To: Sami Wagiaalla's message of Wednesday, 22 August 2007 17:45:14 -0400 <46CCAE6A.3000904@redhat.com>
> But have not merged it with the main trunk yet, as there are some test
> failures.
There is one self-test failure on F8 for ppc32 with the 0.129 sources.
Rawhide has a patch for that.
> I then resolve all the conflicts by blindly favoring upstream.
Please show me all the differences in that tree from the upstream elfutils.
You should not be carrying any.
Thanks,
Roland
next prev parent reply other threads:[~2007-08-22 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 21:45 Sami Wagiaalla
2007-08-22 21:52 ` Roland McGrath [this message]
2007-08-27 19:29 ` Sami Wagiaalla
2007-08-27 20:21 ` Roland McGrath
2007-08-29 20:45 ` Sami Wagiaalla
2007-08-30 20:35 ` Andrew Cagney
2007-08-28 13:25 ` Andrew Cagney
2007-08-27 18:23 ` Sami Wagiaalla
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=20070822215158.AFB804D0418@magilla.localdomain \
--to=roland@redhat.com \
--cc=frysk@sourceware.org \
--cc=swagiaal@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).