From: Keith Seitz <keiths@redhat.com>
To: Dave Lawrence <dlawrence@ad-holdings.co.uk>
Cc: insight@sources.redhat.com
Subject: Re: Version 7.0 No Insight executable built?
Date: Thu, 10 Dec 2009 18:13:00 -0000 [thread overview]
Message-ID: <4B213A21.8070905@redhat.com> (raw)
In-Reply-To: <hfrdb5$lr1$1@ger.gmane.org>
On 12/10/2009 10:06 AM, Dave Lawrence wrote:
> Same problem trying to build with target=arm-elf
Insight was not tagged for that release. Well, it is never tagged until
I do the actual release. Sadly, I have not yet gotten to this. I still
have one or two bugs that I am trying to squash. Or rather, one or two
that I *was* trying to squash.
I'm sitting on some patches to fix x86_64 builds. I'll review those
tonight and see if I cannot get the release done. So far, so good: my
plate is pretty clean.
Keith
prev parent reply other threads:[~2009-12-10 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 18:07 Dave Lawrence
2009-12-10 18:13 ` Keith Seitz [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=4B213A21.8070905@redhat.com \
--to=keiths@redhat.com \
--cc=dlawrence@ad-holdings.co.uk \
--cc=insight@sources.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).