From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: aggressive usurpation of bugs.oe.net by Angstrom
Date: Wed, 30 Jan 2008 22:41:18 +0100 [thread overview]
Message-ID: <fnqqtt$e5o$1@ger.gmane.org> (raw)
In-Reply-To: <20080130203832.31fd5919@widy.localdomain>
Paul Sokolovsky schrieb:
> Let's descend a bit into past then.
No. Please don't do that. And certainly not at this length. It does
not bring us one step closer to a solution.
And as koen has already pointed out, several distros using the same bug
tracker creates problems of its own. Let's try to solve them this time.
No use arguing about the past. Let's argue about the future.
next prev parent reply other threads:[~2008-01-30 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 17:03 RFC: aggressive usurpation of bugs.oe.net by Angstrom Rolf Leggewie
2008-01-30 18:18 ` Rolf Leggewie
2008-01-30 18:38 ` Paul Sokolovsky
2008-01-30 21:41 ` Rolf Leggewie [this message]
2008-01-30 23:56 ` Paul Sokolovsky
2008-01-31 9:49 ` Rolf Leggewie
2008-01-31 11:00 ` Paul Sokolovsky
2008-01-31 11:08 ` Rolf Leggewie
2008-01-31 12:28 ` Richard Purdie
2008-01-31 13:36 ` Paul Sokolovsky
2008-01-30 20:00 ` Koen Kooi
2008-01-31 14:07 ` Paul Sokolovsky
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='fnqqtt$e5o$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.