All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Simon Moeller <dl9pf@gmx.de>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH 1/2] fetch/git: Handle github dropping git:// support
Date: Tue, 02 Nov 2021 15:51:50 +0100	[thread overview]
Message-ID: <3740438.x7lg0THAfG@monster> (raw)
In-Reply-To: <7930bb9f4875fdc32c4fa43395da68bae76a24c0.camel@linuxfoundation.org>

Am Dienstag, 2. November 2021, 14:27:58 CET schrieb Richard Purdie:
>
> With 15 years of legacy branches and recipes out there, this change is
> intended to be backported to older bitbakes to at least give some support
> to people stuck on older versions. This is why this commit and the warning
> are separated.
>
> The warning is being added as we're not at 11.1.22 yet and people have
> previously said they don't like instant hard breaking error messages. We'll
> therefore give people some time to update, then change master to an error.

I think this is a good plan.

Best,
JS




  parent reply	other threads:[~2021-11-02 14:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 12:44 [PATCH 1/2] fetch/git: Handle github dropping git:// support Richard Purdie
2021-11-02 12:45 ` [PATCH 2/2] fetch/git: Show warning for invalid github urls Richard Purdie
2021-11-02 13:19 ` [bitbake-devel] [PATCH 1/2] fetch/git: Handle github dropping git:// support Konrad Weihmann
2021-11-02 13:27   ` Richard Purdie
2021-11-02 14:06     ` Frank Earl
2021-11-02 14:57       ` Quentin Schulz
2021-11-02 14:51     ` Jan-Simon Moeller [this message]
2021-11-02 18:00 ` Peter Kjellerstedt
     [not found] <16B3BB5E65837842.31260@lists.openembedded.org>
2021-11-03 14:13 ` 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
2021-11-11 11:03         ` [bitbake-devel] " Richard Purdie
2021-11-11 12:18           ` gabriel.valcazar
2021-11-11 12:27             ` [bitbake-devel] " Alexander Kanavin

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=3740438.x7lg0THAfG@monster \
    --to=dl9pf@gmx.de \
    --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.