From: "Svend Meyland Nicolaisen" <email@example.com>
Subject: Re: [PATCH] npmsw fetcher: Avoid instantiating Fetch class if url list is empty
Date: Tue, 18 Apr 2023 13:56:19 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 439 bytes --]
next prev parent reply other threads:[~2023-04-18 20:56 UTC|newest]
Thread overview: 6+ 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 [this message]
2023-04-19 7:46 ` Luca Ceresoli
-- strict thread matches above, loose matches on Subject: below --
2023-04-17 9:26 Michael Opdenacker
2023-04-17 21:18 ` Svend Meyland Nicolaisen
2023-04-16 20:07 public
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).