From: "Quentin Schulz" <quentin.schulz@streamunlimited.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] lz4: Use the new branch naming from upstream
Date: Mon, 30 Nov 2020 14:51:31 +0100 [thread overview]
Message-ID: <20201130135131.5vxtbajvhepxc474@qschulz> (raw)
In-Reply-To: <20201130134703.3279682-1-richard.purdie@linuxfoundation.org>
Hi Richard,
On Mon, Nov 30, 2020 at 01:47:03PM +0000, Richard Purdie wrote:
> Upstream renamed master -> dev, update SRC_URI to match.
>
Wondering if "release" branch does not make more sense?
Quentin
next prev parent reply other threads:[~2020-11-30 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 13:47 [PATCH] lz4: Use the new branch naming from upstream Richard Purdie
2020-11-30 13:51 ` Quentin Schulz [this message]
2020-11-30 14:00 ` [OE-core] " 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=20201130135131.5vxtbajvhepxc474@qschulz \
--to=quentin.schulz@streamunlimited.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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