From: Chuck Lever <chuck.lever@oracle.com>
To: Luis Chamberlain <mcgrof@kernel.org>, Daniel Gomez <da.gomez@kernel.org>
Cc: Daniel Gomez <da.gomez@kruces.com>,
"kdevops@lists.linux.dev" <kdevops@lists.linux.dev>
Subject: Re: [PATCH] kconfig: "output yaml" renders boolean N as a comment
Date: Fri, 18 Apr 2025 14:15:29 -0400 [thread overview]
Message-ID: <f33e41fb-0a97-47a0-aa6e-410ea964cf4d@oracle.com> (raw)
In-Reply-To: <8fc66b40-735e-46b8-8375-d3a0570a0983@oracle.com>
On 4/18/25 10:18 AM, Chuck Lever wrote:
> On 4/17/25 11:03 PM, Luis Chamberlain wrote:
>> On Fri, Apr 18, 2025 at 01:13:05AM +0000, Chuck Lever III wrote:
>>>
>>>
>>> After pushing the patch to kconfig / yamlconfig, I tried using
>>> the Makefile.subtrees targets to merge that commit into
>>> kdevops / main, and got this:
>>>
>>> cel@renoir:/tmp/kdevops$ make -f Makefile.subtrees refresh-subtrees
>>> fatal: refusing to merge unrelated histories
>>
>> So.. basically when I removed the old results archive to get the kdevops
>> tree to go on a diet (first patch in the tree now) I git added
>> *everyhing* back... and I forgot to add instead kconfig as a git subtree
>> then. So that messed up the history. There however is a trick which can
>> be adopted for very obscure ways to use git subtrees when this happens,
>> essentially we tell git -- don't worry, trust me.
>>
>> The git ocult trick is documented under kdevops git commit ec5a7d94a3b99e5
>> ("Split 'scripts/kconfig/' into commit 'd2ca2620d14b94bc94e9e0d9adc7a3d030ae13c7'".
>>
>> Its why I documented carefully there as there is no man pages about this
>> fun way to use git subtrees this way. In fact I don't think the authors
>> intended for this to work, but it does.
>
> Well, I should take a step back. The first failure is this:
>
> cel@renoir:/tmp$ git clone git@github.com:linux-kdevops/kdevops.git
> Cloning into 'kdevops'...
> remote: Enumerating objects: 8356, done.
> remote: Counting objects: 100% (2322/2322), done.
> remote: Compressing objects: 100% (515/515), done.
> remote: Total 8356 (delta 2029), reused 1848 (delta 1804), pack-reused
> 6034 (from 2)
> Receiving objects: 100% (8356/8356), 10.94 MiB | 19.18 MiB/s, done.
> Resolving deltas: 100% (4649/4649), done.
> cel@renoir:/tmp$ cd kdevops/
> cel@renoir:/tmp/kdevops$ git remote add kconfig
> git@github.com:linux-kdevops/kconfig.git
> cel@renoir:/tmp/kdevops$ git fetch kconfig
> remote: Enumerating objects: 215, done.
> remote: Counting objects: 100% (215/215), done.
> remote: Compressing objects: 100% (111/111), done.
> remote: Total 215 (delta 125), reused 189 (delta 99), pack-reused 0 (from 0)
> Receiving objects: 100% (215/215), 167.43 KiB | 2.09 MiB/s, done.
> Resolving deltas: 100% (125/125), done.
> From github.com:linux-kdevops/kconfig
> * [new branch] master -> kconfig/master
> * [new branch] yamlconfig -> kconfig/yamlconfig
> cel@renoir:/tmp/kdevops$ git subtree add --prefix=scripts/kconfig
> kconfig master
> fatal: prefix 'scripts/kconfig' already exists.
> cel@renoir:/tmp/kdevops$
>
> I get the same error with:
>
> cel@renoir:/tmp/kdevops$ make -f Makefile.subtrees add-subtree-remotes-dev
> cel@renoir:/tmp/kdevops$ make -f Makefile.subtrees refresh-subtrees
This is what finally worked for me:
$ cd
$ git clone git@github.com:linux-kdevops/kconfig.git
$ cd kconfig
# commit your patches
$ git push origin main:yamlconfig
$ cd
$ git clone git@github.com:linux-kdevops/kdevops.git
$ cd kdevops
$ git remote add kconfig git@github.com:linux-kdevops/kconfig.git
$ git fetch kconfig
$ git subtree pull --squash --prefix=scripts/kconfig kconfig yamlconfig
$ git push origin main:main
Please examine the tip of linux-kdevops/kdevops to make sure all is
well.
${TOPDIR}/Makefile.subtrees appears to be out of date. Perhaps we need a
README.md in scripts/kconfig that explains how to make patches for these
files.
--
Chuck Lever
next prev parent reply other threads:[~2025-04-18 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 15:13 [PATCH] kconfig: "output yaml" renders boolean N as a comment cel
[not found] ` <CABj0suCM=dE8hLHoxZDo+isX5qNZAumF4OCdGqsSVAtoO1DTCw@mail.gmail.com>
[not found] ` <1F522960-C622-4E23-8D74-5F34F32DEAFC@oracle.com>
2025-04-18 3:03 ` Luis Chamberlain
2025-04-18 14:18 ` Chuck Lever
2025-04-18 18:15 ` Chuck Lever [this message]
2025-04-18 19:12 ` Luis Chamberlain
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=f33e41fb-0a97-47a0-aa6e-410ea964cf4d@oracle.com \
--to=chuck.lever@oracle.com \
--cc=da.gomez@kernel.org \
--cc=da.gomez@kruces.com \
--cc=kdevops@lists.linux.dev \
--cc=mcgrof@kernel.org \
/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