From: "Peter A. Bigot" <pab@pabigot.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Denzil updates
Date: Sun, 16 Dec 2012 11:33:06 -0600 [thread overview]
Message-ID: <50CE05D2.8050307@pabigot.com> (raw)
In-Reply-To: <20121216105611.7746c440@eb-e6520>
On 12/16/2012 03:56 AM, Eric Bénard wrote:
> Hi Koen, Hi Liu,
>
> as per your requests the following patches were applied to
> denzil-next :
> 35f92b4 systemd: use system variables instead of hardcoded paths
> 6e0ddd4 systemd: update to v189 66e169f gdm: do not rely on
> dev-tty7.device
> 0f17a3f meta-systemd: systemd-systemctl-native: Also add support for
> WantedBy=*.service
> d6dd53c systemd-systemctl-native: handle ALIAS tag
> e5b3091 systemd-systemctl-native: extend systemctl wrapper to support
> mask action
> f713db3 systemd-systemctl-native: Add additional messages for better
> debugging
>
> patchwork # : 36615 36613 36609 36611 36605 36607 36535 (with manual
> rework for the last one).
>
> Please don't forget to cc me for patches for denzil or danny.
I thought that OE patch submission for any layer should follow the
instructions in the README at the top of the layer being patched.
Those instructions already ask for "[danny]" (e.g.) to be part of the
subject, and for submissions to be mailed to this list. If this isn't
enough and you should be cc'd specifically, can you add your preferred
email address for these messages to the patch instructions?
I'll probably remember to look at the README, but I certainly won't
remember other instructions that pass by on the mailing list like this.
Peter
prev parent reply other threads:[~2012-12-16 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 9:56 Denzil updates Eric Bénard
2012-12-16 17:08 ` Martin Jansa
2012-12-16 17:09 ` Martin Jansa
2012-12-16 17:33 ` Peter A. Bigot [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=50CE05D2.8050307@pabigot.com \
--to=pab@pabigot.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.