From: Michael Rozdoba <mroz@callnetuk.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: splitting deploy/ipk into subarchs
Date: Sat, 24 Feb 2007 11:18:21 +0000 [thread overview]
Message-ID: <45E01EFD.1020707@callnetuk.com> (raw)
In-Reply-To: <45DEA03E.8070903@dominion.kabel.utwente.nl>
Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Matthias Hentges schreef:
>> Am Dienstag, den 20.02.2007, 14:48 +0100 schrieb Koen Kooi:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>> it should be off by default and - by all means - optional.
>
> No it should not. Next time respond to the RFCs instead of starting some uninformed rant
> afterward.
Matthias's post did not read as a rant.
A response earlier certainly would have been more helpful, however as he
points out, if the preceding procedure was meant to be a RFC the period
allowed for this was very short.
How long should be allowed for feedback is an issue I'm not qualified to
comment on, however given the time allowed it is certainly unreasonable
at the very least to complain when constructive feedback is received
after the event.
--
Michael
m r o z a t u k g a t e w a y d o t n e t
prev parent reply other threads:[~2007-02-24 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 11:18 RFC: splitting deploy/ipk into subarchs Koen Kooi
2007-02-19 11:59 ` Marcin Juszkiewicz
2007-02-19 12:30 ` Koen Kooi
2007-02-20 8:19 ` Koen Kooi
2007-02-20 13:48 ` Koen Kooi
2007-02-23 2:26 ` Matthias Hentges
2007-02-23 8:05 ` Koen Kooi
2007-02-24 0:03 ` Matthias Hentges
2007-02-24 11:18 ` Michael Rozdoba [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=45E01EFD.1020707@callnetuk.com \
--to=mroz@callnetuk.com \
--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.