From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Documentation of commit policy and examples
Date: Mon, 09 Aug 2010 05:42:01 -0700 [thread overview]
Message-ID: <4C5FF799.8090400@balister.org> (raw)
In-Reply-To: <1281354065.3767.15.camel@mattotaupa>
On 08/09/2010 04:41 AM, Paul Menzel wrote:
> Dear Wolfgang,
>
>
> Am Montag, den 09.08.2010, 12:25 +0200 schrieb Hauser, Wolfgang (external):
>> I would do it myself, but as I am a newbee in OE, git, patchwork and bitbake, I don't have the know how to create a real good HowTo.
>> That should be done by experts.
>
> well, the “experts” thought that the current documentation [1, 3] in the
> Wiki is good enough. So it would be great if you told us what is
> missing. (Since I think all your questions are answered on these pages.)
Experts don't read the documenation :) I know they should at least check
it from time to time though.
Philip
prev parent reply other threads:[~2010-08-09 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 8:12 [PATCH] busybox: fix defconfig handling problems triggered by "configure according to {MACHINE, DISTRO}_FEATURES"; added inetd handling (resent) Hauser, Wolfgang (external)
2010-08-09 9:27 ` Paul Menzel
2010-08-09 9:40 ` Hauser, Wolfgang (external)
2010-08-09 10:02 ` Paul Menzel
2010-08-09 10:25 ` Hauser, Wolfgang (external)
2010-08-09 11:41 ` Documentation of commit policy and examples (was: busybox: fix defconfig handling problems triggered by "configure according to {MACHINE, DISTRO}_FEATURES"; added inetd handling (resent)) Paul Menzel
2010-08-09 12:42 ` Philip Balister [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=4C5FF799.8090400@balister.org \
--to=philip@balister.org \
--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.