From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>,
Yoann Congal <yoann.congal@smile.fr>
Subject: Re: [bitbake-devel] bitbake-setup update problem
Date: Thu, 29 Jan 2026 14:42:14 +0100 [thread overview]
Message-ID: <6327151f-ccda-4b63-9757-e50acd6b6853@gmail.com> (raw)
In-Reply-To: <DB5PR02MB10213E60D96F5D4AE9C5DBB93EF89A@DB5PR02MB10213.eurprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
On 20.01.2026 14:48, Peter Kjellerstedt wrote:
> I'm not sure why you are pointing at repo here, because this is actually
> a use case that repo handles extremely well. We have been using repo for
> over ten years to maintain the manifests for all our builds, and (AFAIK)
> we have not had a single case of repo loosing any data due to doing an
> update.
I didn't mean that it loses the data. I meant the need to run some other
command _using_ repo so it is aware of what happens in the repository.
Slava
[-- Attachment #2: Type: text/html, Size: 944 bytes --]
prev parent reply other threads:[~2026-01-29 13:42 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
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 [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=6327151f-ccda-4b63-9757-e50acd6b6853@gmail.com \
--to=uvv.mail@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--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