QEMU0002  0aa*j"T~*bѿ   5_I|Mdv &K Index of /FSS-BCZ/root/lib/python3.9/site-packages/tuned/ppd

Index of /FSS-BCZ/root/lib/python3.9/site-packages/tuned/ppd

 NameLast modifiedSizeDescription
 Parent Directory   -  
 tuned-ppd.policy 2026-02-22 14:49 1.3K 
 dbus.conf 2026-02-22 14:49 639  
 tuned-ppd.service 2026-02-22 14:49 315  
 ppd.conf 2026-02-22 14:49 249  
 tuned-ppd.dbus.service 2026-02-22 14:49 87  
 __pycache__/ 2026-07-24 04:52 -  
" li~TmJqAme1h e  ## HOW TO CONTRIBUTE Thank you for considering contributing to this distribution. This file contains instructions that will help you work with the source code. The distribution is managed with Dist::Zilla. This means that many of the usual files you might expect are not in the repository, but are generated at release time, as is much of the documentation. Some generated files are kept in the repository as a convenience (e.g. Makefile.PL or cpanfile). Generally, **you do not need Dist::Zilla to contribute patches**. You do need Dist::Zilla to create a tarball. See below for guidance. ### Getting dependencies If you have App::cpanminus 1.6 or later installed, you can use `cpanm` to satisfy dependencies like this: $ cpanm --installdeps . Otherwise, look for either a `Makefile.PL` or `cpanfile` file for a list of dependencies to satisfy. ### Running tests You can run tests directly using the `prove` tool: $ prove -l $ prove -lv t/some_test_file.t For most of my distributions, `prove` is entirely sufficient for you to test any patches you have. I use `prove` for 99% of my testing during development. ### Code style and tidying Please try to match any existing coding style. If there is a `.perltidyrc` file, please install Perl::Tidy and use perltidy before submitting patches. If there is a `tidyall.ini` file, you can also install Code::TidyAll and run `tidyall` on a file or `tidyall -a` to tidy all files. ### Patching documentation Much of the documentation Pod is generated at release time. Some is generated boilerplate; other documentation is built from pseudo-POD directives in the source like C<=method> or C<=func>. If you would like to submit a documentation edit, please limit yourself to the documentation you see. If you see typos or documentation issues in the generated docs, please email or open a bug ticket instead of patching. ### Where to send patches and pull requests If you found this distribution on Github, sending a pull-request is the best way to contribute. If a pull-request isn't possible, a bug t