From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Yoann Congal <yoann.congal@smile.fr>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] bitbake-setup update problem
Date: Mon, 22 Dec 2025 10:14:02 +0100 [thread overview]
Message-ID: <1dc33b07-759f-499f-82cb-84e5c20f77ec@gmail.com> (raw)
In-Reply-To: <CAMSfU+71B0VQvP7U5BPDcgY++q=PMY3pfTOWdOREXorwAAU9bA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
On 22.12.2025 10:09, Yoann Congal wrote:
>
>
> Le lun. 22 déc. 2025 à 09:56, Vyacheslav Yurkov via
> lists.openembedded.org <http://lists.openembedded.org>
> <uvv.mail=gmail.com@lists.openembedded.org> a écrit :
>
> It turned out to be a painful discovery.
> I wanted to rebase my custom branch in oe-core on top of latest
> master
> before publishing a set of patches. But it seems like after running
> 'bitbake-setup update' my branch is nowhere to be seen. Is it
> supposed
> to be like that? Any chance to get it restored?
>
>
> Try "git reflog HEAD", you should see every commit HEAD has been on
> (and, in theory, the commit at the tip of your branch)
That's the first thing I'd tried. The whole layer seems to be a fresh clone.
Slava
[-- Attachment #2: Type: text/html, Size: 1979 bytes --]
next prev parent reply other threads:[~2025-12-22 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 8:56 bitbake-setup update problem Vyacheslav Yurkov
2025-12-22 9:09 ` [bitbake-devel] " Yoann Congal
2025-12-22 9:14 ` Vyacheslav Yurkov [this message]
2025-12-22 11:18 ` Alexander Kanavin
[not found] ` <1883858B93EFC423.1614991@lists.openembedded.org>
2025-12-22 11:25 ` Alexander Kanavin
[not found] ` <188385EDFF4B6429.1342979@lists.openembedded.org>
2026-01-02 20:19 ` Alexander Kanavin
[not found] ` <18870377D56AF168.1986633@lists.openembedded.org>
2026-01-08 12:14 ` Alexander Kanavin
2026-01-18 8:48 ` Vyacheslav Yurkov
2026-01-20 13:48 ` Peter Kjellerstedt
2026-01-28 12:34 ` Alexander Kanavin
2026-01-29 13:42 ` Vyacheslav Yurkov
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=1dc33b07-759f-499f-82cb-84e5c20f77ec@gmail.com \
--to=uvv.mail@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
/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