Skip to contentSkip to conversation

Denzil updates

DISCUSSION Eric Bénard 3 participants 4 messages Dec 16, 2012

lore
Share & tools
lore
#0 lore raw

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.

Thanks
Eric

#1 lore raw
Quoted 15 lines · Eric Bénard

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

Quoted 4 lines

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.

did git push show some errors/warnings when searching for patchwork commits to mark as applied? interestingly none was marked by hook

http://patches.openembedded.org/bundle/jama/denzil/

Cheers,

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#2 lore raw
Quoted 19 lines · Martin Jansa
Quoted 18 lines · Eric Bénard

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).

Quoted 6 lines
Quoted 1 line

Please don't forget to cc me for patches for denzil or danny.

did git push show some errors/warnings when searching for patchwork commits to mark as applied? interestingly none was marked by hook

http://patches.openembedded.org/bundle/jama/denzil/

nvm, I haven't noticed that it's only in denzil-next

Cheers,

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#3 lore raw
In reply to Eric Bénard
Quoted 15 lines · Eric Bénard

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

Quoted 4 lines

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