Rivoreo Source Code Repositories
src.rivoreo.one / systemd-stable / v232-stable
commitcc56e4f00e8b8cb3a1037ad300837cb3a015079b[log] [download]
authorLennart Poettering <lennart@poettering.net>Tue Nov 20 04:34:08 2018 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>Tue Jan 22 20:25:03 2019 +0100
treeee20cda79801be9f2d2d7537bd2d49373c224b26
parent7d2ba4dec81746f8cd0fbbbb00efbc59cc2267ad [diff]
tree-wide: use __ prefixed gcc attributes (#10843)

As suggest here:

https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute-Syntax

    "You may optionally specify attribute names with ‘__’ preceding and
    following the name. This allows you to use them in header files without
    being concerned about a possible macro of the same name. For example,
    you may use the attribute name __noreturn__ instead of noreturn. "

(cherry picked from commit 012c2f761bf1eb0b9c784b867293f7f1c17c3080)
6 files changed
tree: ee20cda79801be9f2d2d7537bd2d49373c224b26
  1. .dir-locals.el
  2. .editorconfig
  3. .gitattributes
  4. .github/
  5. .gitignore
  6. .mailmap
  7. .mkosi/
  8. .travis.yml
  9. .vimrc
  10. .ycm_extra_conf.py
  11. CODING_STYLE
  12. DISTRO_PORTING
  13. HACKING
  14. LICENSE.GPL2
  15. LICENSE.LGPL2.1
  16. Makefile-man.am
  17. Makefile.am
  18. NEWS
  19. README
  20. README.md
  21. TODO
  22. autogen.sh
  23. catalog/
  24. coccinelle/
  25. configure.ac
  26. docs/
  27. factory/etc/
  28. hwdb/
  29. m4/
  30. man/
  31. mkosi.build
  32. mkosi.default ⇨ .mkosi/mkosi.fedora
  33. network/
  34. po/
  35. rules/
  36. shell-completion/
  37. src/
  38. sysctl.d/
  39. system-preset/
  40. sysusers.d/
  41. test/
  42. tmpfiles.d/
  43. tools/
  44. units/
  45. xorg/
README.md

systemd - System and Service Manager

Build Status
Coverity Scan Status

Details

General information about systemd can be found in the systemd Wiki.

Information about build requirements are provided in the README file.

Consult our NEWS file for information about what's new in the most recent systemd versions.

Please see the HACKING file for information how to hack on systemd and test your modifications.

Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.

When preparing patches for systemd, please follow our Coding Style Guidelines.

If you are looking for support, please contact our mailing list or join our IRC channel.