Thanks for helping me! On Sat, May 31, 2025 at 11:55:01AM +0800, Congcong Kuo wrote: > Sorry for typo, you may still need `-o topic`. > > $ git push origin contrib-linux-libre:refs/for/kernel-updates -o > topic="kernel updates"
I realized that for my first kernel pull request, which was successful, I actually used the refspec 'contrib-linux-libre:refs/for/master'. The salient difference is that this pull request was for the master branch. I just made a pull request like this successfully. I guess this is how I have to do it. https://codeberg.org/guix/guix/pulls/360 > I don’t test how shell and git will process spaces in the topic name. Maybe > It’s a good practice that don’t put spaces in topic. I agree it's a bit risky, but I always like to push my luck with the use of "normal" whitespace and see if it works. Because it would be great to make our tools support it if possible... after 50+ years of Unix :) In this case, the Codeberg user interface says this: lfam wants to merge 2 commits from lfam/kernel updates into master So, it seems like it can handle the whitespace, at least partially.
