/
githubmirror
/
libusb
Обзор
Документация
Войти
/
githubmirror
/
libusb
Код
Запросы
0
Пакеты
0
Релизы
0
Аналитика
Безопасность
master
HACKING
29 строк
1 KB
Ihor Dutchak
deprecate LIBUSB_NANO; use libusb_version::describe instead (#1839)
03 июн 2026, 09:15
Не верифицирован
03 июн 2026, 09:15
d3f0f0c
Код
Авторство
О чём код?
Contributing to libusb ********************** For larger changes or API changes/extensions it may be wise to first discuss on the mailing list or in the issue tracker before larger coding efforts are initiated. If you extend or change the API make sure documentation is updated. Please run make -C doc and check for any Doxygen warnings. Commit messages should be formatted to 72 chars width and have a free-standing summary line. See for instance "Commit Guidelines" on https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project or https://cbea.ms/git-commit/ about how to make well-formed commit messages. Put detailed information in the commit message itself, which will end up in the git history. On the other hand the description that you fill in the GitHub pull request web page does not go anywhere. For copyright reasons it is preferable to have your full name in the commit author field. Do not update the AUTHOR file yourself, the maintainers will update it as part of the release preparation. LIBUSB_NANO (libusb/version_nano.h) is deprecated since 1.0.31 and is no longer updated; please don't touch it in your patches or pull requests. A unique-per-build identifier is available at runtime via libusb_version::describe, generated from `git describe --tags --always --dirty` at build time. See libusb.h for details.