Dev

[David-letian]

Note: Please adhere to Contributing Guidelines.

Summary

Update this section with information on why change is necessary,
what it exactly does and how, if new feature shows up, provide
references (dependencies, similar problems and solutions), etc.

Impact

Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.

Testing

This section should provide a detailed description of what you did
to verify your changes work and do not break existing code.

Please provide information about your host machine, the board(s) you
tested your changes on, and how you tested. Logs should be included.

For example, when changing something in the core OS functions, you
may want to run the OSTest application to verify that there are no
regressions. Changes to ADC code may warrant running the adc
example. Adding a new uORB driver may require that you run
uorb_listener to verify correct operation.

Pure documentation changes can just be tested with make html
(see docs) and verification of the correct format in your
browser.

PRs without testing information will not be accepted. We will
request test logs.

[xiaoxiang781216]

why the patch is empty

[acassis]

why the patch is empty

Very strange, it is a 60 bytes binary

[acassis]

@David-letian Could you please explain what you were planning to do?

[acassis]

@David-letian seems like you are messing with git, now there are tittle in the commits, but they are empty. Please study how to use git and read the NuttX contributing guide:
https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md

or the more detailed version:
https://nuttx.apache.org/docs/latest/contributing/index.html