From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: should i submit detailed bugs for e2fsprogs and gnome-games?
Date: Thu, 17 Dec 2009 14:02:39 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912171402080.2265@localhost> (raw)
In-Reply-To: <4B2A77E5.1040804@balister.org>
On Thu, 17 Dec 2009, Philip Balister wrote:
> I saw the gnome-games problem. Steve says he has a later version in
> his repo, when he figure out some other things we hope that update
> solves the problem.
but the e2fsprogs build problem is all mine, is it? *sigh*. i'll
see what i can figure out.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2009-12-17 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 16:39 should i submit detailed bugs for e2fsprogs and gnome-games? Robert P. J. Day
2009-12-17 18:26 ` Philip Balister
2009-12-17 19:02 ` Robert P. J. Day [this message]
2009-12-19 12:37 ` Paul Menzel
2009-12-19 13:01 ` Robert P. J. Day
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=alpine.LFD.2.00.0912171402080.2265@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.