All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
	Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/2] insane: native-last: Print classes inherited after native/nativesdk
Date: Thu, 28 Jan 2021 23:16:13 +0000	[thread overview]
Message-ID: <f7478654da009d76e9bc6c7a1ba3a99865f775e6.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKow4MBA-WoGMJyxiU-75GXY3-BQyWRqT+dYsJ=+AT7ECQ@mail.gmail.com>

On Thu, 2021-01-28 at 17:27 -0300, Otavio Salvador wrote:
> Em qua., 27 de jan. de 2021 às 18:30, Tomasz Dziendzielski
> <tomasz.dziendzielski@gmail.com> escreveu:
> > 
> > See [YOCTO #5729] for details.
> > 
> > Signed-off-by: Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com>
> 
> I'd prefer a little of context on the commit log.

Agreed, I've improved the log of the patch I've merged. Linking to a
bugzilla entry isn't really enough information. I appreciate the
patches though, there have been some good ones!

Cheers,

Richard


  reply	other threads:[~2021-01-28 23:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 21:33 [PATCH 1/2] insane: Add missing INSANE_SKIP mechanism for native-last QA check Tomasz Dziendzielski
2021-01-27 21:33 ` [PATCH 2/2] insane: native-last: Print classes inherited after native/nativesdk Tomasz Dziendzielski
2021-01-28 20:27   ` [OE-core] " Otavio Salvador
2021-01-28 23:16     ` Richard Purdie [this message]
2021-01-28 23:46       ` Tomasz Dziendzielski

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=f7478654da009d76e9bc6c7a1ba3a99865f775e6.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=tomasz.dziendzielski@gmail.com \
    /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.