From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: RFC after the fact - bug 1987
Date: Fri, 16 Mar 2007 17:16:34 +0100 [thread overview]
Message-ID: <etecci$200$1@sea.gmane.org> (raw)
Hi,
it seems I have still a few things to learn as far as updating OE
metadata goes. Furthermore it seems I might have created the first
major fuck-up. I apologize for the inconvenience this has caused to the
OE community.
Now, to sort things out; I committed
a96c9acac99b5599d2b0fb0a518603646414d166 yesterday to fix bug 1987. It
seemed like an obvious case (move debug files into -dbg package) which
is why I dared to commit. psokolovsky made me aware that an RFC had
been necessary to make this commit to a core part of OE and that it
might have broken compilation for some OE users.
Now here I am trying to do The Right Thing[TM]. I want to discuss "mtn
diff -r e9d53f524190d295cb769c7594711fd76eb197b7 -r
a96c9acac99b5599d2b0fb0a518603646414d166". Please let me know if there
is anything wrong with this change. If it should be reverted, feel free
to do so or let me know via mail or IRC and I will fix it pronto.
Regards
Rolf
next reply other threads:[~2007-03-16 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 16:16 Rolf Leggewie [this message]
2007-03-16 17:00 ` RFC after the fact - bug 1987 Paul Sokolovsky
2007-03-16 18:43 ` Rolf Leggewie
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='etecci$200$1@sea.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.