From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] useradd.bbclass: do not let depend native packages on base-passwd from target
Date: Thu, 17 Nov 2011 22:44:46 +0100 [thread overview]
Message-ID: <1321566286.3335.12.camel@mattotaupa> (raw)
In-Reply-To: <CABcZANmNDjxSjjocJH80Jq8r_iSNy7L2ABASKOtKSWa1GEo6Qw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
Am Donnerstag, den 17.11.2011, 14:37 -0700 schrieb Chris Larson:
> On Thu, Nov 17, 2011 at 9:26 AM, Paul Menzel wrote:
> > Am Donnerstag, den 17.11.2011, 10:48 +0100 schrieb Henning Heinold:
> >
> >> with the setup now in useradd.bbclass, at least dbus-native depends
> >> on the base-passwd from target. I think this is not wanted.
> >> My patch resets the DEPENDS line for native packages similar to
> >> nativesdk.
> >
> > why do not you use that as the commit message? That would be very
> > helpful for me at least. ;-)
>
> The summary often describes the what, the detailed description the
> how. The summary here is accurate, particularly regarding the
> behavioral change, rather than the implementation details.
I did refer to that. Looking at the patch’s commit message you will see
it is empty. So just sending the patch with no patch introduction and
putting the message from the patch introduction into the patch’s commit
message would benefit everyone.
Thanks,
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2011-11-17 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 9:48 [PATCH] useradd.bbclass: do not let depend native packages on base-passwd from target Henning Heinold
2011-11-17 9:48 ` Henning Heinold
2011-11-17 9:56 ` Richard Purdie
2011-11-17 16:26 ` Paul Menzel
2011-11-17 17:00 ` Henning Heinold
2011-11-17 21:37 ` Chris Larson
2011-11-17 21:44 ` Paul Menzel [this message]
2011-11-22 19:46 ` Saul Wold
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=1321566286.3335.12.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox