Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Christos Gavros" <gavrosc@yahoo.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sanity: check variable GO_IMPORT
Date: Tue, 25 Feb 2025 12:37:59 -0800	[thread overview]
Message-ID: <18144.1740515879050354566@lists.openembedded.org> (raw)
In-Reply-To: <aa7f692a-ec61-4053-9524-7f0bc24c4e53@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 160 bytes --]

hi Randy

I did a build and I wrote a comment in the bug15763 that is generating an error!
I always built and test as much as I can before sending patches.

[-- Attachment #2: Type: text/html, Size: 210 bytes --]

  reply	other threads:[~2025-02-25 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250225180939.21341-1-gavrosc.ref@yahoo.com>
2025-02-25 18:09 ` [PATCH] sanity: check variable GO_IMPORT Christos Gavros
2025-02-25 20:33   ` Randy MacLeod
2025-02-25 20:37     ` Christos Gavros [this message]
2025-02-25 22:43     ` [OE-core] " Richard Purdie
2025-02-26 10:00       ` Christos Gavros
2025-02-27 13:15         ` Christos Gavros
2025-02-27 13:20           ` [OE-core] " Richard Purdie

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=18144.1740515879050354566@lists.openembedded.org \
    --to=gavrosc@yahoo.com \
    --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