From: "Rahul Chauhan" <rahulchauhankitps@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Proposal to change the SRC_URI source reference of neard package.
Date: Sun, 27 Mar 2022 11:57:37 -0700 [thread overview]
Message-ID: <15514.1648407457453010645@lists.openembedded.org> (raw)
In-Reply-To: <CAAnfSTtfH14DNySVhDGYp76OH84TZ8EdZMTT5X_Sn_-gogjCGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
Dear Ross,
Thanks For your Quick response.
As per your Recommendation, I have sent a mail to "linux-nfc@lists.01.org" and inform that below tarball is incomplete.
https://cdn.kernel.org/pub/linux/network/nfc/neard-0.16.tar.gz
and request, to upload the correct tarball or is there any specific reason of the missing files.
If you are okay, I will release a patch to do a proper git clone instead of fetching tarball until tarball is fixed.
Please confirm!
Thanks & Regards
Rahul Kumar
[-- Attachment #2: Type: text/html, Size: 566 bytes --]
next prev parent reply other threads:[~2022-03-27 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 5:21 Proposal to change the SRC_URI source reference of neard package Rahul Chauhan
2022-03-27 10:24 ` [OE-core] " Ross Burton
2022-03-27 18:57 ` Rahul Chauhan [this message]
2022-03-27 19:37 ` Khem Raj
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=15514.1648407457453010645@lists.openembedded.org \
--to=rahulchauhankitps@gmail.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