Well, I'm not really sure I would need it in most cases. For instance today I was modifying an existing device tree to make it fit my board, that's not necessarily going to last.
Or say I have a package, which is from my company and doesn't have any reason to get out of it. As an integrator I need to modify the build system, let's say something in the makefile, or maybe there's simply stuff that I don't want on my system. So I'll make a patch. Why would Yocto be authority for the way my commits are formatted? In all the above cases I don't see why. Yann CARDAILLAC, On Wed, Jul 10, 2024 at 5:26 PM Alexander Kanavin <alex.kana...@gmail.com> wrote: > On Wed, 10 Jul 2024 at 15:45, Yann CARDAILLAC via > lists.yoctoproject.org <ycnakajsph=gmail....@lists.yoctoproject.org> > wrote: > > I'm not having the issue anymore, but I don't want to do that for all > the patches I'm going to backport, can you explain why and when this error > occurs? And if it's systematic how can I systematically ignore it as I > don't really care about the "Upstream-Status". > > Having a well-defined upstream-status in every patch is a layer > maintenance practice we do want to encourage. You might not care about > this information right now, but you might want it a few months from > now. Or someone else working with your layer might want it when they > need to rebase the software being patched to some different version. > It will help them find where the original commit is, or give them a > reason why the patch was never submitted upstream and shouldn't be > etc. We have a rich nomenclature that covers almost every scenario. > > If you're backporting patches, put 'Upstream-Status: Backport [link > from where]' into them. 'Pending' without a reason is basically same > as 'no status', and even though it's currently allowed, the > restrictions on it will get tighter over time. > > Alex >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63473): https://lists.yoctoproject.org/g/yocto/message/63473 Mute This Topic: https://lists.yoctoproject.org/mt/107142644/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
