public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Patrick Williams" <patrick@stwcx.xyz>
To: Konrad Weihmann <kweihmann@outlook.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta-oe][PATCH] catch2: upgrade to 2.13.4
Date: Tue, 16 Feb 2021 09:02:49 -0600	[thread overview]
Message-ID: <YCvemU+yJrokjLks@heinlein> (raw)
In-Reply-To: <AM9PR09MB46427D7AB75584EE2F517F3BA8879@AM9PR09MB4642.eurprd09.prod.outlook.com>

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

On Tue, Feb 16, 2021 at 03:03:33PM +0100, Konrad Weihmann wrote:
> On 16.02.21 14:43, Patrick Williams wrote:
  
> > -SRC_URI = "git://github.com/catchorg/Catch2.git"
> > -SRCREV = "2c869e17e4803d30b3d5ca5b0d76387b9db97fa5"
> > +SRC_URI = "git://github.com/catchorg/Catch2.git;nobranch=1"
> 
> Wrong mailing list I suppose - this should go to 
> openembedded-devel@lists.openembedded.org 

Oh, sorry.  I was following:
    https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

> and on a second note I don't 
> think using nobranch is a good idea - the branch used "v2.x" or is there 
> any reason for this which isn't that obvious?

Let me try 'branch=v2.x'.  `fetch` failed when I left it as default so I
didn't investigate a whole lot more and just used 'nobranch=1' because
that was the first thing that came to mind.  It does look like the
v2.13.4 tag is along the v2.x branch, so that'll probably work.

> 
> > +SRCREV = "de6fe184a9ac1a06895cdd1c9b437f0a0bdf14ad"
> >   
-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

      reply	other threads:[~2021-02-16 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 13:43 [meta-oe][PATCH] catch2: upgrade to 2.13.4 Patrick Williams
2021-02-16 14:03 ` [OE-core] " Konrad Weihmann
2021-02-16 15:02   ` Patrick Williams [this message]

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=YCvemU+yJrokjLks@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=kweihmann@outlook.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