-Original Message-
From: Alexander Kanavin
Sent: Tuesday, November 14, 2023 2:28 PM
> I'm fine with that. Can you tweak the tools?
Yeah I will, just need some time to work on this,
so it might take a bit of time.
Sincerely,
Jermain Horsman
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive
On Wed, 8 Nov 2023 at 16:03, Jermain Horsman wrote:
> This is certainly a possibility, there isn't really any issue with this,
> however, it will checkout using a detached head which can be a
> bit of an annoyance if you do a subsequent create-layers-setup
> as all the branches will have changed
-Original Message-
From: Alexander Kanavin
Sent: Wednesday, November 8, 2023 12:24 PM
> I think adding this field can be avoided if remote and branch are
> combined with / separator in the already existig 'rev' field?
>
> E.g. 'git checkout poky-contrib/master' and 'git checkout
>
I think adding this field can be avoided if remote and branch are
combined with / separator in the already existig 'rev' field?
E.g. 'git checkout poky-contrib/master' and 'git checkout
origin/master' both work here. The idea is that 'rev' contains
basically what we give to 'git checkout' in the
From: Jermain Horsman
Having a default remote present allows for the checkout of a
branch in the case multiple remotes are available.
This requires an update to the json-schema and associated checks.
Signed-off-by: Jermain Horsman
---
meta/files/layers.example.json| 5
