All of lore.kernel.org
 help / color / mirror / Atom feed
From: gabriel.valcazar@digi.com
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/2] fetch/git: Handle github dropping git:// support
Date: Wed, 10 Nov 2021 07:15:32 -0800	[thread overview]
Message-ID: <22842.1636557332722004495@lists.openembedded.org> (raw)
In-Reply-To: <CA+chaQc1n4sZDrNvBN5HGebqWLKLSXFr2w9xDEKhQMEfg_dOrQ@mail.gmail.com>

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

Thanks all for the suggestions. Indeed, creating a fork of poky and applying the fix ourselves seems like a reasonable solution if there is no official fix for old versions.

I've just tested applying the patch to *bitbake 1.18* , and I'm able to build my Yocto 1.4 distribution with no problem. Is it not possible to officially backport the patch all the way back to bitbake 1.18? I could provide the patches, but they're literally just clean cherry-picks of the bitbake 1.40 patch.

Regards,
Gabriel

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

  reply	other threads:[~2021-11-10 15:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16B3BB5E65837842.31260@lists.openembedded.org>
2021-11-03 14:13 ` [bitbake-devel] [PATCH 1/2] fetch/git: Handle github dropping git:// support Richard Purdie
2021-11-09 15:40   ` gabriel.valcazar
2021-11-09 15:44     ` [bitbake-devel] " Alexander Kanavin
2021-11-09 15:47     ` Martin Jansa
2021-11-10 15:15       ` gabriel.valcazar [this message]
2021-11-11 11:03         ` Richard Purdie
2021-11-11 12:18           ` gabriel.valcazar
2021-11-11 12:27             ` [bitbake-devel] " Alexander Kanavin
     [not found] <c491c84fa505853c5744defe9466302b5276e1e4.camel@linuxfoundation.org>
2021-11-11 13:24 ` gabriel.valcazar
2021-11-02 12:44 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=22842.1636557332722004495@lists.openembedded.org \
    --to=gabriel.valcazar@digi.com \
    --cc=bitbake-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.