From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <alex.kanavin@gmail.com>, "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] dev manual inconsistently encourages changing "poky" checkout locally
Date: Fri, 20 Jun 2025 12:03:08 +0200 [thread overview]
Message-ID: <DAR9WH6OG420.2QTYQU9FHEXRD@bootlin.com> (raw)
In-Reply-To: <CANNYZj-oUWVgEaw=2NfYhhEA3bNPPtwvHb4j4a0EtB1iSVBZmw@mail.gmail.com>
On Fri Jun 20, 2025 at 11:47 AM CEST, Alexander Kanavin via lists.yoctoproject.org wrote:
> On Fri, 20 Jun 2025 at 11:44, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>> it's point 5 here:
>>
>> https://docs.yoctoproject.org/what-i-wish-id-known.html
>
> "Never modify the POKY layer. Never. Ever. When you update to the next
> release, you’ll lose all of your work. ALL OF IT."
>
> I'm not sure what this point wants to say to be honest. Can't make sense of it.
While the what-i-wish-id-known document is pretty clear about it, it's true that
saying "As you work with the local branch, you can periodically use the git pull
--rebase command to be sure you are up-to-date with the upstream branch." when
speaking about the poky repository kind of imply local modifications. And these
two documents are unrelated.
So all-in-all, I think what we want to remove here is the "--rebase" flag.
That's the only thing implying local modifications to poky. Using "git pull" is
fine. I'd take a patch.
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-06-20 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 9:05 dev manual inconsistently encourages changing "poky" checkout locally Robert P. J. Day
2025-06-20 9:26 ` [docs] " Alexander Kanavin
2025-06-20 9:44 ` Robert P. J. Day
2025-06-20 9:47 ` Alexander Kanavin
2025-06-20 10:03 ` Antonin Godard [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=DAR9WH6OG420.2QTYQU9FHEXRD@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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