public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Barker <paul@pbarker.dev>
To: hjenemark@gmail.com, Openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [scarthgap] git tags not present in upstream repo
Date: Wed, 08 Apr 2026 10:54:28 +0100	[thread overview]
Message-ID: <c654ad89e15b45c555b7388d75db910a7f05fa46.camel@pbarker.dev> (raw)
In-Reply-To: <CAFx0Op0o1LkXfe253sQHJTULuYn1=Tw-BzZqfxSOPx7UNUf_Sw@mail.gmail.com>

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

On Wed, 2026-04-08 at 11:20 +0200, Hans-Jacob Enemark via
lists.openembedded.org wrote:
> Hi
> In the process of updating a fork of oe-core, I have noticed that series of
> tags are present in the fork that I'm managing and not in the upstream repo
> at git.openembedded.org/openembedded-core
> 
> The latest tags I have that are pointing to the same commit are:
> yocto-5.0.11, 2024-04.11-scarthgap, 2024-04.11.
> 
> I don't see the last two tags on the upstream repo.
> 
> Did you make a cleanup of tags at some point during the last six months or
> do I have to find other mirrors to sync my fork to?
> 
> Thanks in advance for the answer.

Hi Hans-Jacob,

We've cleaned up obsolete duplicate tags recently to fix regression report
issues and make things less confusing for users [1].

[1]: https://lore.kernel.org/yocto/CADfgfoZ2-_Vypjx4mDypmh=Hace4+gm5_4S-aN=Zad6O_CKw9A@mail.gmail.com/

Best regards,

-- 
Paul Barker


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

      reply	other threads:[~2026-04-08  9:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08  9:20 [scarthgap] git tags not present in upstream repo Hans-Jacob Enemark
2026-04-08  9:54 ` Paul Barker [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=c654ad89e15b45c555b7388d75db910a7f05fa46.camel@pbarker.dev \
    --to=paul@pbarker.dev \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=hjenemark@gmail.com \
    /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