Hi, I am fairly new myself, but I think I can answer your questions.
On 10/8/25 20:03, Yuxuan Chen wrote:
1. For the legal requirements, most likely I will need to use the Developer Certificate of Origin. Does that mean I will just need to do `git commit --signoff`?
As far as I am aware, yes, that should be it.
2. Are there any easy ways to format the code? Due to the unfamiliarity I have with the GNU style, conforming to the coding standards takes a long time. For example, my editor is not well set up to take a mixture of tabs and spaces. Is it typical for contributors to manually format the code or is there a script I am missing?There are scripts in contrib that verify your code is formatted correctly. There are also clang-format and editorconfig files, if your editor supports them. Not sure about how other developers format their code, but I use the clang-format config and it works just fine.
3. I tried to run all existing tests with `make && make -C gcc -k check` and there are a small quantity of existing (unexpected) failures. Is that an indication that I don't have the right setup?Not necessarily, it's normal for the testsuite to fail. They way you verify your patches is by running the testsuite once with no changes, then running it again with your patch applied and comparing the results, for example by diffing the outputs of the test_summary script in contrib.
4. For subsequent submissions after these modifications, can I just compute a new patch and attach it in a reply-all to this email chain?What people usually do is they start a new thread for each version of the patch (hence the v2, v3,... you can see in the subjects of some emails sent to this mailing list). You should also document what changes you've made since the last version you sent.
Yuxuan
Best regards, Josef
smime.p7s
Description: S/MIME Cryptographic Signature
