From: Peter Stuge <peter@stuge.se>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] [bugzilla-daemon@gentoo.org: [Bug 326991] Testing release of sys-libs/zlib-1.2.5.3 from unofficial sources (???)]
Date: Tue, 6 Jul 2010 12:30:33 +0200 [thread overview]
Message-ID: <20100706103033.21783.qmail@stuge.se> (raw)
In-Reply-To: <20100705232904.GB581@nibiru.local>
Hi Enrico,
Enrico Weigelt wrote:
> does he speak for all of you ?
OSS-QM strikes me personally as an odd solution. It could of course
be the right thing to do just the same, but I guess you will have to
make it more popular before it becomes a de-facto standard.
If you feel strongly about it (I guess you do) then I would suggest
that you make your own Gentoo overlay with all the packages. That way
it's be easy for anyone interested to test it out.
//Peter
next prev parent reply other threads:[~2010-07-06 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 23:29 [gentoo-embedded] [bugzilla-daemon@gentoo.org: [Bug 326991] Testing release of sys-libs/zlib-1.2.5.3 from unofficial sources (???)] Enrico Weigelt
2010-07-06 1:55 ` solar
2010-07-06 10:30 ` Peter Stuge [this message]
2010-07-06 13:31 ` Ed W
2010-07-06 14:16 ` Peter Stuge
2010-07-06 15:38 ` wireless
2010-07-07 3:58 ` solar
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=20100706103033.21783.qmail@stuge.se \
--to=peter@stuge.se \
--cc=gentoo-embedded@lists.gentoo.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