bitbake-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Svend Meyland Nicolaisen" <public@smn.dk>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH] npmsw fetcher: Avoid instantiating Fetch class if url list is empty
Date: Wed, 19 Apr 2023 09:46:01 +0200	[thread overview]
Message-ID: <20230419094601.534c38c2@booty> (raw)
In-Reply-To: <17294.1681851379281342528@lists.openembedded.org>

Hi Svend,

On Tue, 18 Apr 2023 13:56:19 -0700
"Svend Meyland Nicolaisen" <public@smn.dk> wrote:

> Hi Luca,
> 
> Thank you for your mail. I am sorry that I forgot the sign-off option the second time around. I have now sent the patch again including sign-off and tagged as PATCH v2.
> 
> I could however not get the -v option on git commit to work. As far as I can see the -v option means verbose. I used --subject-prefix on git send-email instead. I hope everything is OK now.

Ah, sure, my mistake: the -v<N> option is for git format-patch, not git
commit. Apologies.

Best regards,
Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2023-04-19  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 21:12 [PATCH] npmsw fetcher: Avoid instantiating Fetch class if url list is empty Svend Meyland Nicolaisen
2023-04-18 10:24 ` [bitbake-devel] " Luca Ceresoli
2023-04-18 20:56   ` Svend Meyland Nicolaisen
2023-04-19  7:46     ` Luca Ceresoli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-16 20:07 public
2023-04-17  7:53 ` [bitbake-devel] " Luca Ceresoli
2023-04-17  9:26   ` Michael Opdenacker
2023-04-17 21:18     ` Svend Meyland Nicolaisen
2023-04-18  8:11       ` [bitbake-devel] " Michael Opdenacker

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=20230419094601.534c38c2@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=public@smn.dk \
    /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;
as well as URLs for NNTP newsgroup(s).