From: "Ranjitsinh Rathod" <ranjitsinhrathod1991@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [master][langdale][kirkstone][dunfell][PATCH] glibc-version.inc: Use https protocol for fetch task
Date: Tue, 03 Jan 2023 05:49:48 -0800 [thread overview]
Message-ID: <29497.1672753788020339166@lists.openembedded.org> (raw)
In-Reply-To: <52dceb5d7867a60a1da6c6f5879f4d949c9be483.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 235 bytes --]
Hi Rechard,
Thanks for the input.
But is it okay to change protocol from git to https. I can change the commit message if it is possible
I hope it will not harm anything if we change the protocol, right?
Thanks,
Ranjitsinh
[-- Attachment #2: Type: text/html, Size: 267 bytes --]
next prev parent reply other threads:[~2023-01-03 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 12:34 [OE-Core][master][langdale][kirkstone][dunfell][PATCH] glibc-version.inc: Use https protocol for fetch task Ranjitsinh Rathod
2023-01-03 12:40 ` Richard Purdie
2023-01-03 13:49 ` Ranjitsinh Rathod [this message]
2023-01-03 13:53 ` [OE-core] [master][langdale][kirkstone][dunfell][PATCH] " Alexander Kanavin
2023-01-03 13:56 ` Ranjitsinh Rathod
2023-01-03 14:02 ` [OE-core] " Richard Purdie
2023-01-03 18:50 ` 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=29497.1672753788020339166@lists.openembedded.org \
--to=ranjitsinhrathod1991@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