neulab/tldr huggingface dataset:
• Removed support for Ubuntu 16.04 (#59869)
• Removed the deprecated support for gid_from_name from the user state module (#60565)
• Removed deprecated virt.migrate_non_shared, virt.migrate_non_shared_inc, ssh from virt.migrate, and python2/python3 args from salt.utils.thin.gen_min and .gen_thin (#60893)
Deprecated • utils/boto3_elasticsearch is no longer needed (#59882)
• Changed "manufacture" grain to "manufacturer" for Solaris on SPARC to unify the name across all platforms. The old "manufacture" grain is now deprecated and will be removed in Sulfur (#60511)
Changed • Changed nginx.version to return version without nginx/ prefix. (#57111)
• Updated Slack webhook returner to support event returns on salt-master (#57182)
• Parsing Epoch out of version during pkg remove, since yum can't handle that in all of the cases. (#57881)
• Add extra onfail req check in the state engine to allow onfail to be used with onchanges and other reqs in the same state (#59026)
• Changed the default character set used by utils.pycrypto.secure_password() to include symbols and implemented arguments to control the used character set. (#59486)
Fixed • Surface strerror to user state instead of returning false (#20789)
• Fixing _get_envs() to preserve the order of pillar_roots. _get_envs() returned pillar_roots in a non-deterministic order. (#24501)
• Fixes salt-cloud KeyError that occurs when there exists any subnets with no tags when profiles use subnetname (#44330)
• Fixes postgres_local_cache by removing duplicate unicode encoding. (#46942)
• Fixing the state aggregation system to properly handle requisities. Fixing pkg state to exclude packages from aggregation if the hold attribute is in the state. (#47628)
• fix issue that allows case sensitive files to be carried through (#47969)
• Allow GCE Salt Cloud to use previously created IP Addresses. (#48947)
• Fixing rabbitmq.list_user_permissions to ensure we are returning a permission list with three elements even when some values are empty. (#49115)
• Periodically restart the fileserver update process to avoid leaks (#50313)
• Fix default value to dictionary for mine_function (#50695)
• Allow user.present to work on Alpine Linux by fixing linux_shadow.info (#50979)
• Ensure that zypper is called with only one --no-refresh parameter (#51382)
• Fixed fileclient cachedir path switching from master to minion due to incorrect MasterMinion configuration (#52288)
• Fixed the container detection inside virtual machines (#53868)
• Fix invalid dnf command when obsoletes=True in pkg.update function (#54224)
• Jinja renderer resolves wrong relative paths when importing subdirectories (#55159)
• Fixed bug #55262 where salt.modules.iptables would call cmd.run and receive and interpret interspersed stdout and stderr output from subprocesses. (#55262)
• Updated pcs support to handle auth and setup for new syntax supporting version 0.10 (#56924)
• Reinstate ignore_cidr option in salt-cloud openstack driver (#57127)
• Fix for network.wolmatch runner displaying 'invalid arguments' error with valid arguements (#57473)
• Fixed bug 57490, which prevented package installation for Open Euler and Issabel PBX. Both Open Euler and Issabel PBX use Yum for package management, added them to yumpkg.py. (#57490)
• Better handling of bad RSA public keys from minions (#57733)
• Fixing various functions in the file state module that use user.info to get group information, certain hosts particularly proxy minions do not have the user.info function avaiable. (#57786)
• Do not monkey patch yaml loaders: Prevent breaking Ansible filter modules (#57995)
• Fix --subset command line option, and support old 'sub' parameter name in cmd_subset for backwards compatibility (#58600)
• When calling salt.utils.http.query with a HEAD method to check for the existence of a source ensure that decode_body is False, so the file is not downloaded into memory when we don't need the contents. (#58881)
• Update the runas user on freebsd for postgres versions >9.5, since freebsd will be removing the package on 2021-05-13. (#58915)
• Fix pip module linked requirements file parsing (#58944)
• Fix incorrect hostname quoting in /etc/sysconfig/networking on Red Hat family OS. (#58956)
• Fix Xen DomU virt detection in grains for long running machines. (#59001)
• add encoding when windows encoding is not defaulting to utf8 (#59063)
• Fix "aptpkg.normalize_name" in case the arch is "all" for DEB packages (#59269)
• Astra Linux now considered a Debian family distro (#59332)
• Reworking the mysql module and state so that passwordless does not try to use unix_socket until unix_socket is set to True. (#59337)
• Fixed the zabbix module to read the connection data from pillar. (#59338)
• Fix crash on "yumpkg" execution module when unexpected output at listing patches (#59354)
• Remove return that had left over py2 code from win_path.py (#59396)
• Don't create spicevmc channel for Xen virtual machines (#59416)
• Fix win_servermanager.install so it will reboot when restart=True is passed (#59424)
• Clear the cached network interface grains during minion init and grains refresh (#59490)
• Normalized grain output for LXC containers (#59573)
• Fix typo in 'salt/states/cmd.py' to use "comment" instead of "commnd". (#59581)
• add aliyun linux support and set alinux as redhat family (#59686)
• Don't fail updating network without netmask ip attribute (#59692)
• Fixed using reserved keyword 'set' as function argument in modules/ipset.py (#59714)
• Return empty changes when nothing has been done in virt.defined and virt.running states (#59739)
• Fix an issue with the LGPO module when the gpt.ini file contains unix style line endings (/n). This was happening on a Windows Server 2019 instance created in Google Cloud Platform (GCP). (#59769)
• The ansiblegate module now correctly passes keyword arguments to Ansible module calls (#59792)
• Make sure cmdmod._log_cmd handles tuples properly (#59793)
• Updating the add, delete, modify, enable_job, and disable_job functions to return appropriate changes. (#59844)
• Apply pre-commit changes to entire codebase. (#59847)
• Fix Hetzner cloud driver does not recognize machines when rolling out a map (#59864)
• Update Windows build deps & DLLs, Use Python 3.8, libsodium.dll 1.0.18, OpenSSL dlls to 1.1.1k (#59865)
• Salt api verifies proper log file path when providing '--log-file' from the cli (#59880)
• Detect Mendel Linux as Debian (#59892)
• Fixed compilation of requisite_ins by also checking state type along with name/id (#59922)
• Fix xen._get_vm() to not break silently when a VM and a template on XenServer have the same name. (#59932)
• Added missing space for nftables.build_rule when using saddr or daddr. (#59958)
• Fixed interrupting salt-call in a pdb session. (#59966)
• Validate we can import map files in states (#60003)
• Update alter_db to return True or False depending on the success of failure of the alter.  Update grant_exists to only use the full list of available privileges when the grant is on the global level, eg. datbase is ".". (#60031)
• Fixed firewalld.list_zones when any "rich rules" is set (#60033)
• IPCMessageSubscriber objects expose their connect method as a corotine so they can be wrapped by SyncWrapper. (#60049)
• Allow for Napalm dependency netmiko_mod to load correctly when used by Napalm with Cisco IOS (#60061)
• Ensure proper access to the created temporary file when runas is passed to cmd.exec_code_all (#60072)
• Fixed an IndexError in pkgng.latest_version when querying an unknown package. (#60105)
• Fixed pkgng.latest_version when querying by origin (e.g. "shells/bash"). (#60108)
• Gracefuly handle errors in virt.vm_info (#60132)
• The LGPO Module now uses "Success and Failure" for normal audit settings and advanced audit settings (#60142)
• Fixing tests/pytests/unit/utils/scheduler/test_eval.py tests so the sleep happens before the status, so the job is given time before we check it. (#60149)
• Fixed ValueError exception in state.show_state_usage (#60179)
• Redact the username and password when something goes wrong when using an HTTP source and we raise an exception. (#60203)
• Inject the Ansible functions into Salt's ansiblegate module which was broken on the 3001 release. (#60207)
• Figure out the available Python version inside containers when executing "dockermod.call" function (#60229)
• Handle IPv6 route types such as anycast, multicast, etc when returned from IPv6 route table queries (#60232)
• Move the commonly used code that converts a list to a dictionary into salt.utils.beacons.  Fixing inotify beacon close function to ensure the configuration is converted from the provided list format into a dictionary. (#60241)
• Set name of engine subprocesses (#60259)
• Properly discover block devices path in virt.running (#60296)
• Avoid exceptions when handling some exception cases. (#60330)
• Fixed faulty error message in npm.installed state. (#60339)
• Port option reinstated for Junos Proxy (accidentally removed) (#60340)
• Now hosts.rm_host can remove entries from /etc/hosts when this file have inline comments. (#60351)
• Fixes issue where the full same name is not used when making rights assignments with group policy (#60357)
• Fixed zabbix_host.present to not overwrite inventory_mode to "manual" everytime inventory is updated. (#60382)
• Allowed zabbix_host.present to do partial updates of inventory, also don't erase everything if inventory is missing in state definition. (#60389)
• Fixing the mysql_cache module to handle binary inserting binary data into the database. Initially adding tests. (#60398)
• Fixed host_inventory_get to not throw an exception if host does not exist (#60418)
• Check for /dev/kvm to detect KVM hypervisor. (#60419)
• Fixing file.accumulated handling of dependencies when the state_id is used instead of {function: state_id} format. (#60426)
• Adding the ability for yumpkg.remove to handle package names with widdcards. (#60461)
• Pass emulator path to get guest capabilities from libvirt (#60491)
• virt.get_disks: properly report qemu-img errors (#60512)
• Make all platforms have psutils. This prevents a minion from starting if an instance is all ready running. (#60523)
• Remove check for TIAMAT_BUILD enforcing USE_STATIC_REQUIREMENTS, this is now controled by Tiamat v7.10.1 and above (#60559)
• Have the beacon call run through a try...except, catching any errors, logging and firing an event that includes the error.  Fixing the swapusage beacon to ensure value is a string before we attempt to filter out the %. (#60585)
• Refactor loader into logical sub-modules (#60594)
• Clean up references to ZMQDefaultLoop (#60617)
• change dep warn from Silicon to Phosphorus for the cmd,show,system_info and add_config functions in the nxos module. (#60669)
• Fix bug 60602 where the hetzner cloud provider isn't recognized correctly (#60675)
• Fix the pwd.getpwnam caching issue on macOS user module (#60676)
• Fixing beacons that can include a value in their configuration that may or may not included a percentage.  We want to handle the situation where the percentage sign is not included and the value is not handled as a string. (#60684)
• Fix RuntimeError in process manager (#60749)
• Ensure all data that is being passed along to LDAP is in an OrderedSet and contains bytes. (#60760)
• Update the AWS API version so VMs spun up by salt-cloud where the VPC has it enabled to assign ipv6 addresses by default, actually get ipv6 addresses assigned by default. (#60804)
• Remove un-needed singletons from tranports (#60851)
• Deprecate salt.payload.Serial (#60953)
Added • Add windows support for file.patch with patch.exe from git for windows optional packages (#44783)
• Added ability to pass exclude kwarg to salt.state inside orchestrate. (#49130)
• Added success_stdout and success_stderr arguments to cmd.run, to override default return code behavior. (#50597)
• The netbox pillar now been enhanced to add support for querying virtual machines (in addition to devices), as well as minion interfaces and associated IP addresses. (#51490)
• Add support for transactional systems, like openSUSE MicroOS (#58519)
• Added namespace headers to allow use of namespace from config to communicate with Vault Enterprise namespaces (#58585)
• boto3mod unit tests (#58713)
• New decorators allow_one_of() and require_one_of() (#58742)
• Added nosync switch to disable initial raid synchronization (#59193)
• Expanded the documentation for the netbox pillar. (#59398)
• Rocky Linux has been added to the RedHat os_family. (#59682)
• Add "poudriere -i -j jail_name" option to list jail information for poudriere (#59831)
• Added the grains.uuid on Windows platform (#59888)
• Add a salt.util.platform check to detect the AArch64 64-bit extension of the ARM architecture. (#59915)
• Adding support for Deltaproxy controlled proxy minions into Salt Open. (#60090)
• Added functions to slsutil execution module to test if files exist in the state tree Added funtion to slsutil execution module to search for a file by walking up the state tree (#60159)
• Allow module_refresh to also refresh available beacons, eg. following a Python library being installed and "refresh_modules" being passed as an argument in a state. (#60541)
• Add the detect_remote_minions and remote_minions_port options to allow the master to detect remote ports for connected minions. This will allow users to detect Heist-Salt minions the master is connected to over port 22 by default. (#60612)
• Add the python rpm-vercmp library in the rpm_lowpkg.py module. (#60814)
• Allow a user to use the aptpkg.py module without installing python-apt. (#60818)
SEE ALSO: Legacy salt-cloud release docs
SEE ALSO: Legacy salt-api release docs
Introduction First, you need to configure the master file. This is because all module functions require either a configured api_key (for Cloud) or a ttp_user with a tpp_password and a base_url (for Trust Platform).
For Venafi Cloud:
venafi: api_key: abcdef01-2345-6789-abcd-ef0123456789 base_url: "https://cloud.venafi.example.com/"    (optional)
If you don't have a Venafi Cloud account, you can sign up for one on the enrollment page.
For Venafi Platform:
venafi: base_url: "https://tpp.example.com/" tpp_user: admin tpp_password: "Str0ngPa$$w0rd" trust_bundle: "/opt/venafi/bundle.pem"
It is not common for the Venafi Platform's REST API (WebSDK) to be secured using a certificate issued by a publicly trusted CA, therefore establishing trust for that server certificate is a critical part of your configuration. Ideally this is done by obtaining the root CA certificate in the issuing chain in PEM format and copying that file to your Salt Master (e.g. /opt/venafi/bundle.pem). You then reference that file using the 'trust_bundle' parameter as shown above.
For the Venafi module to create keys and certificates it is necessary to enable external pillars. This is done by adding the following to the /etc/salt/master file:
Runner Functions request This command is used to enroll a certificate from Venafi Cloud or Venafi Platform.
minion_id ID of the minion for which the certificate is being issued. Required.
dns_name DNS subject name for the certificate. Required if csr_path is not specified.
csr_path Full path name of certificate signing request file to enroll. Required if dns_name is not specified.
zone   Venafi Cloud zone ID or Venafi Platform folder that specify key and certificate policy. Defaults to "Default". For Venafi Cloud, the Zone ID can be found in the Zone page for your Venafi Cloud project.
org_unit Business Unit, Department, etc. Do not specify if it does not apply.
org    Exact legal name of your organization. Do not abbreviate.
loc    City/locality where your organization is legally located.
state  State or province where your organization is legally located. Must not be abbreviated.
country Country where your organization is legally located; two-letter ISO code.
key_password Password for encrypting the private key.
The syntax for requesting a new certificate with private key generation looks like this:
salt-run venafi.request minion.example.com dns_name=www.example.com \ country=US state=California loc=Sacramento org="Company Name" org_unit=DevOps \ zone=Internet key_password=SecretSauce
And the syntax for requesting a new certificate using a previously generated CSR looks like this:
salt-run venafi.request minion.example.com csr_path=/tmp/minion.req zone=Internet
show_cert This command is used to show last issued certificate for domain.
dns_name DNS subject name of the certificate to look up.
salt-run venafi.show_cert www.example.com
list_domain_cache This command lists domains that have been cached on this Salt Master.
del_cached_domain This command deletes a domain from the Salt Master's cache.
domains A domain name, or a comma-separated list of domain names, to delete from this master's cache.
salt-run venafi.del_cached_domain www.example.com
Transfer certificate to a minion To transfer a cached certificate to a minion, you can use Venafi pillar.
Example state (SLS) file:
/etc/ssl/cert/www.example.com.crt: file.managed: - contents_pillar: venafi:www.example.com:cert - replace: True
/etc/ssl/cert/www.example.com.key: file.managed: - contents_pillar: venafi:www.example.com:pkey - replace: True
/etc/ssl/cert/www.example.com-chain.pem: file.managed: - contents_pillar: venafi:www.example.com:chain - replace: True
Auto-Order The evaluation of states in the order that they are defined in a SLS file. See also: ordering.
Bootstrap A stand-alone Salt project which can download and install a Salt master and/or a Salt minion onto a host. See also: salt-bootstrap.
Compound Matcher A combination of many target definitions that can be combined with boolean operators. See also: targeting.
EAuth  Shorthand for 'external authentication'. A system for calling to a system outside of Salt in order to authenticate users and determine if they are allowed to issue particular commands to Salt. See also: external auth.
Environment A directory tree containing state files which can be applied to minions. See also: top file.
Execution Function A Python function inside an Execution Module that may take arguments and performs specific system-management tasks. See also: the list of execution modules.
External Job Cache An external data-store that can archive information about jobs that have been run. A default returner. See also: ext_job_cache, the list of returners.
Execution Module A Python module that contains execution functions which directly perform various system-management tasks on a server. Salt ships with a number of execution modules but users can also write their own execution modules to perform specialized tasks. See also: the list of execution modules.
External Pillar A module that accepts arbitrary arguments and returns a dictionary.  The dictionary is automatically added to a pillar for a minion.
Event  A notice emitted onto an event bus. Events are often driven by requests for actions to occur on a minion or master and the results of those actions. See also: Salt Reactor.
File Server A local or remote location for storing both Salt-specific files such as top files or SLS files as well as files that can be distributed to minions, such as system configuration files. See also: Salt's file server.
Grain  A key-value pair which contains a fact about a system, such as its hostname, network addresses. See also: targeting with grains.
Highdata The data structure in a SLS file the represents a set of state declarations. See also: state layers.
Highstate The collection of states to be applied to a system. See also: state layers.
Idempotent An action that ensures the system is in a well-known state regardless of the system's state before the action is applied.  A corollary to this is that applying the action multiple times results in no changes to the system.  State module functions should be idempotent.  Some state module functions, such as cmd.run are not idempotent by default but can be made idempotent with the proper use of requisites such as unless and onlyif. For more information, see wikipedia.
Jinja  A templating language which allows variables and simple logic to be dynamically inserted into static text files when they are rendered.  See also: Salt's Jinja documentation.
Job    The complete set of tasks to be performed by the execution of a Salt command are a single job. See also: jobs runner.
Job Cache A storage location for job results, which may then be queried by a salt runner or an external system. May be local to a salt master or stored externally.
Job ID A unique identifier to represent a given job.  This is often shortened to JID.
Low State The collection of processed states after requisites and order are evaluated. See also: state layers.
Master A central Salt daemon from which commands can be issued to listening minions.
Masterless A minion which does not require a Salt master to operate. All configuration is local. See also: file_client.
Master Tops A system for the master that allows hooks into external systems to generate top file data.
Mine   A facility to collect arbitrary data from minions and store that data on the master. This data is then available to all other minions.  (Sometimes referred to as Salt Mine.) See also: Salt Mine.
Minion A server running a Salt minion daemon which can listen to commands from a master and perform the requested tasks. Generally, minions are servers which are to be controlled using Salt.
Minion ID A globally unique identifier for a minion. See also: id.
Multi-Master The ability for a minion to be actively connected to multiple Salt masters at the same time in high-availability environments.
Node Group A pre-defined group of minions declared in the master configuration file. See also: targeting.
Outputter A formatter for defining the characteristics of output data from a Salt command. See also: list of outputters.
Peer Communication The ability for minions to communicate directly with other minions instead of brokering commands through the Salt master. See also: peer communication.
Pillar A simple key-value store for user-defined data to be made available to a minion. Often used to store and distribute sensitive data to minions.  See also: Pillar, list of Pillar modules.
Proxy Minion A minion which can control devices that are unable to run a Salt minion locally, such as routers and switches.
PyDSL  A Pythonic domain-specific-language used as a Salt renderer. PyDSL can be used in cases where adding pure Python into SLS files is beneficial.  See also: PyDSL.
Reactor An interface for listening to events and defining actions that Salt should taken upon receipt of given events. See also: Reactor.
Render Pipe Allows SLS files to be rendered by multiple renderers, with each renderer receiving the output of the previous. See also: composing renderers.
Renderer Responsible for translating a given data serialization format such as YAML or JSON into a Python data structure that can be consumed by Salt.  See also: list of renderers.
Returner Allows for the results of a Salt command to be sent to a given data-store such as a database or log file for archival. See also: list of returners.
Roster A flat-file list of target hosts. (Currently only used by salt-ssh.)
Runner Module A module containing a set of runner functions. See also: list of runner modules.
Runner Function A function which is called by the salt-run command and executes on the master instead of on a minion. See also: Runner Module.
Salt Cloud A suite of tools used to create and deploy systems on many hosted cloud providers. See also: salt-cloud.
Salt SSH A configuration management and remote orchestration system that does not require that any software besides SSH be installed on systems to be controlled.
Salt Thin A subset of the normal Salt distribution that does not include any transport routines. A Salt Thin bundle can be dropped onto a host and used directly without any requirement that the host be connected to a network. Used by Salt SSH. See also: thin runner.
Salt Virt Used to manage the creation and deployment of virtual machines onto a set of host machines. Often used to create and deploy private clouds.  See also: virt runner.
SLS Module Contains a set of state declarations.
State Compiler Translates highdata into lowdata.
State Declaration A data structure which contains a unique ID and describes one or more states of a system such as ensuring that a package is installed or a user is defined. See also: highstate structure.
State Function A function contained inside a state module which can manages the application of a particular state to a system. State functions frequently call out to one or more execution modules to perform a given task.
State Module A module which contains a set of state functions. See also: list of state modules.
State Run The application of a set of states on a set of systems.
Syndic A forwarder which can relay messages between tiered masters. See also: Syndic.
Target Minion(s) to which a given salt command will apply. See also: targeting.
Top File Determines which SLS files should be applied to various systems and organizes those groups of systems into environments. See also: top file, list of master top modules.
__virtual__ A function in a module that is called on module load to determine whether or not the module should be available to a minion. This function commonly contains logic to determine if all requirements for a module are available, such as external libraries.
Worker A master process which can send notices and receive replies from minions. See also: worker_threads.
Thomas S. Hatch <thatch45@gmail.com> and many others, please see the Authors file
LATEX(1)                     General Commands Manual                    LATEX(1)
latex, pdflatex, xelatex, lualatex, dvilualatex, cslatex, pdfcslatex, platex, uplatex, lamed - structured text formatting and typesetting
latex [first-line]
This manual page is a mere skeleton.
The LaTeX language is described in the book LaTeX - A Document Preparation System.  LaTeX is a TeX macro package, not a modification to the TeX source program, so all the capabilities described in tex(1) are present.
The LaTeX macros encourage writers to think about the content of their documents, rather than the form.  The ideal, very difficult to realize, is to have no formatting commands (like ``switch to italic'' or ``skip 2 picas'') in the document at all; instead, everything is done by specific markup instructions: ``emphasize'', ``start a section''.
The primary source of documentation for LaTeX is the LaTeX manual referenced below.
lualatex, pdflatex, pdfcslatex, xelatex are LaTeX formats based on the respective engines.  All output PDF by default. platex, uplatex are Japanese LaTeX formats based on e-pTeX and e-upTeX (DVI output). lamed is the Aleph-based LaTeX format (DVI output). dvilualatex is LuaTeX-based and outputs DVI. cslatex is csTeX-based (primitives integrated into pdfTeX) and outputs DVI.
On some systems latex209 and slitex may still be available for compatibility with older versions of LaTeX.  These should not be used for new texts.
amstex(1), luatex(1), pdftex(1), ptex(1), tex(1), xetex(1).
Leslie Lamport, LaTeX - A Document Preparation System, Addison-Wesley, 1985, ISBN 020115790X.
Frank Mittelbach, Michel Goossens, Johannes Braams, David Carlisle, and Chris Rowley, LaTeX Companion, Addison-Wesley, 2004, ISBN 0201362996 (2nd edition).
The LaTeX home page is http://latex-project.org. A list of some LaTeX tutorials is at http://www.tex.ac.uk/cgi- bin/texfaq2html?label=man-latex. An unofficial reference manual for LaTeX is at https://ctan.org/pkg/latex2e-help-texinfo.
GIT-LOG(1)                         Git Manual                         GIT-LOG(1)
git-log - Show commit logs
git log [<options>] [<revision range>] [[--] <path>...]
Shows the commit logs.
$ git log foo bar ^baz
$ git log origin..HEAD $ git log HEAD ^origin
$ git log A B --not $(git merge-base --all A B) $ git log A...B
The command takes options applicable to the git-rev-list(1) command to control what is shown and how, and options applicable to the git-diff(1) command to control how the changes each commit introduces are shown.
--follow Continue listing the history of a file beyond renames (works only for a single file).
--no-decorate, --decorate[=short|full|auto|no] Print out the ref names of any commits that are shown. If short is specified, the ref name prefixes refs/heads/, refs/tags/ and refs/remotes/ will not be printed. If full is specified, the full ref name (including prefix) will be printed. If auto is specified, then if the output is going to a terminal, the ref names are shown as if short were given, otherwise no ref names are shown. The option --decorate is short-hand for --decorate=short. Default to configuration value of log.decorate if configured, otherwise, auto.
--decorate-refs=<pattern>, --decorate-refs-exclude=<pattern> If no --decorate-refs is given, pretend as if all refs were included. For each candidate, do not use it for decoration if it matches any patterns given to --decorate-refs-exclude or if it doesn’t match any of the patterns given to --decorate-refs. The log.excludeDecoration config option allows excluding refs from the decorations, but an explicit --decorate-refs pattern will override a match in log.excludeDecoration.
--source Print out the ref name given on the command line by which each commit was reached.
--[no-]mailmap, --[no-]use-mailmap Use mailmap file to map author and committer names and email addresses to canonical real names and email addresses. See git- shortlog(1).
--full-diff Without this flag, git log -p <path>...  shows commits that touch the specified paths, and diffs about the same specified paths. With this, the full diff is shown for commits that touch the specified paths; this means that "<path>..." limits only commits, and doesn’t limit diff for those commits.
Note that this affects all diff-based output types, e.g. those produced by --stat, etc.
--log-size Include a line “log size <number>” in the output for each commit, where <number> is the length of that commit’s message in bytes. Intended to speed up tools that read log messages from git log output by allowing them to allocate space in advance.
<revision range> Show only commits in the specified revision range. When no <revision range> is specified, it defaults to HEAD (i.e. the whole history leading to the current commit).  origin..HEAD specifies all the commits reachable from the current commit (i.e.  HEAD), but not from origin. For a complete list of ways to spell <revision range>, see the Specifying Ranges section of gitrevisions(7).
[--] <path>... Show only commits that are enough to explain how the files that match the specified paths came to be. See History Simplification below for details and other simplification modes.
This option also changes default diff format for merge commits to first-parent, see --diff-merges=first-parent for details.
Commit Formatting --pretty[=<format>], --format=<format> Pretty-print the contents of the commit logs in a given format, where <format> can be one of oneline, short, medium, full, fuller, reference, email, raw, format:<string> and tformat:<string>. When <format> is none of the above, and has %placeholder in it, it acts as if --pretty=tformat:<format> were given.
--notes[=<ref>] Show the notes (see git-notes(1)) that annotate the commit, when showing the commit log message. This is the default for git log, git show and git whatchanged commands when there is no --pretty, --format, or --oneline option given on the command line.
By default, the notes shown are from the notes refs listed in the core.notesRef and notes.displayRef variables (or corresponding environment overrides). See git-config(1) for more details.
With an optional <ref> argument, use the ref to find the notes to display. The ref can specify the full refname when it begins with refs/notes/; when it begins with notes/, refs/ and otherwise refs/notes/ is prefixed to form a full name of the ref.
Multiple --notes options can be combined to control which notes are being displayed. Examples: "--notes=foo" will show only notes from "refs/notes/foo"; "--notes=foo --notes" will show both notes from "refs/notes/foo" and from the default notes ref(s).
--no-notes Do not show notes. This negates the above --notes option, by resetting the list of notes refs from which notes are shown. Options are parsed in the order given on the command line, so e.g. "--notes --notes=foo --no-notes --notes=bar" will only show notes from "refs/notes/bar".
--show-notes[=<ref>], --[no-]standard-notes These options are deprecated. Use the above --notes/--no-notes options instead.
%N commit notes
By default, git log does not generate any diff output. The options below can be used to show the changes made by each commit.
Note that unless one of --diff-merges variants (including short -m, -c, and --cc options) is explicitly given, merge commits will not show a diff, even if a diff format like --patch is selected, nor will they match search options like -S. The exception is when --first-parent is in use, in which case first-parent is the default format.
-p, -u, --patch Generate patch (see section on generating patches).
--diff-merges=(off|none|on|first-parent|1|separate|m|combined|c|dense-combined|cc), --no-diff-merges Specify diff format to be used for merge commits. Default is off unless --first-parent is in use, in which case first-parent is the default.
--diff-merges=(off|none), --no-diff-merges Disable output of diffs for merge commits. Useful to override implied value.
--diff-merges=on, --diff-merges=m, -m This option makes diff output for merge commits to be shown in the default format.  -m will produce the output only if -p is given as well. The default format could be changed using log.diffMerges configuration parameter, which default value is separate.
--diff-merges=first-parent, --diff-merges=1 This option makes merge commits show the full diff with respect to the first parent only.
--diff-merges=separate This makes merge commits show the full diff with respect to each of the parents. Separate log entry and diff is generated for each parent.
--diff-merges=combined, --diff-merges=c, -c With this option, diff output for a merge commit shows the differences from each of the parents to the merge result simultaneously instead of showing pairwise diff between a parent and the result one at a time. Furthermore, it lists only files which were modified from all parents.  -c implies -p.
--diff-merges=dense-combined, --diff-merges=cc, --cc With this option the output produced by --diff-merges=combined is further compressed by omitting uninteresting hunks whose contents in the parents have only two variants and the merge result picks one of them without modification.  --cc implies -p.
--combined-all-paths This flag causes combined diffs (used for merge commits) to list the name of the file from all parents. It thus only has effect when --diff-merges=[dense-]combined is in use, and is likely only useful if filename changes are detected (i.e. when either rename or copy detection have been requested).
--raw For each commit, show a summary of changes using the raw diff format. See the "RAW OUTPUT FORMAT" section of git-diff(1). This is different from showing the log itself in raw format, which you can achieve with --format=raw.
-t Show the tree objects in the diff output.
-z Separate the commits with NULs instead of with new newlines.
Also, when --raw or --numstat has been given, do not munge pathnames and use NULs as output field terminators.
--color[=<when>] Show colored diff.  --color (i.e. without =<when>) is the same as --color=always.  <when> can be one of always, never, or auto.
--no-color Turn off colored diff. It is the same as --color=never.
--color-moved[=<mode>] Moved lines of code are colored differently. The <mode> defaults to no if the option is not given and to zebra if the option with no mode is given. The mode must be one of:
--color-moved-ws=<modes> This configures how whitespace is ignored when performing the move detection for --color-moved. These modes can be given as a comma separated list:
-M[<n>], --find-renames[=<n>] If generating diffs, detect and report renames for each commit. For following files across renames while traversing history, see --follow. If n is specified, it is a threshold on the similarity index (i.e. amount of addition/deletions compared to the file’s size). For example, -M90% means Git should consider a delete/add pair to be a rename if more than 90% of the file hasn’t changed. Without a % sign, the number is to be read as a fraction, with a decimal point before it. I.e., -M5 becomes 0.5, and is thus the same as -M50%. Similarly, -M05 is the same as -M5%. To limit detection to exact renames, use -M100%. The default similarity index is 50%.
git log --no-merges Show the whole commit history, but skip any merges
git log v2.6.12.. include/scsi drivers/scsi Show all commits since version v2.6.12 that changed any file in the include/scsi or drivers/scsi subdirectories
git log --since="2 weeks ago" -- gitk Show the changes during the last two weeks to the file gitk. The -- is necessary to avoid confusion with the branch named gitk
git log --name-status release..test Show the commits that are in the "test" branch but not yet in the "release" branch, along with the list of paths each commit modifies.
git log --follow builtin/rev-list.c Shows the commits that changed builtin/rev-list.c, including those commits that occurred before the file was given its present name.
git log --branches --not --remotes=origin Shows all commits that are in any of local branches but not in any of remote-tracking branches for origin (what you have that origin doesn’t).
git log master --not --remotes=*/master Shows all commits that are in local master but not in any remote repository master branches.
git log -p -m --first-parent Shows the history including change diffs, but only from the “main branch” perspective, skipping commits that come from merged branches, and showing full diffs of changes introduced by the merges. This makes sense only when following a strict policy of merging all topic branches when staying on a single integration branch.
git log -L '/int main/',/^}/:main.c Shows how the function main() in the file main.c evolved over time.
git log -3 Limits the number of commits to show to 3.
See git-config(1) for core variables and git-diff(1) for settings related to diff generation.
format.pretty Default for the --format option. (See Pretty Formats above.) Defaults to medium.
i18n.logOutputEncoding Encoding to use when displaying logs. (See Discussion above.) Defaults to the value of i18n.commitEncoding if set, and UTF-8 otherwise.
log.date Default format for human-readable dates. (Compare the --date option.) Defaults to "default", which means to write dates like Sat May 8 19:35:34 2010 -0500.
If the format is set to "auto:foo" and the pager is in use, format "foo" will be the used for the date format. Otherwise "default" will be used.
log.follow If true, git log will act as if the --follow option was used when a single <path> is given. This has the same limitations as --follow, i.e. it cannot be used to follow multiple files and does not work well on non-linear history.
log.showRoot If false, git log and related commands will not treat the initial commit as a big creation event. Any root commits in git log -p output would be shown without a diff attached. The default is true.
log.showSignature If true, git log and related commands will act as if the --show-signature option was passed to them.
mailmap.* See git-shortlog(1).
notes.displayRef Which refs, in addition to the default set by core.notesRef or GIT_NOTES_REF, to read notes from when showing commit messages with the log family of commands. See git-notes(1).
May be an unabbreviated ref name or a glob and may be specified multiple times. A warning will be issued for refs that do not exist, but a glob that does not match any refs is silently ignored.
This setting can be disabled by the --no-notes option, overridden by the GIT_NOTES_DISPLAY_REF environment variable, and overridden by the --notes=<ref> option.
GLIB-COMPILE-RESOU(1)             User Commands            GLIB-COMPILE-RESOU(1)
glib-compile-resources - GLib resource compiler
glib-compile-resources [OPTION...] {FILE}
glib-compile-resources reads the resource description from FILE and the files that it references and creates a binary resource bundle that is suitable for use with the GResource API. The resulting bundle is then written out as-is, or as C source for linking into an application.
The XML resource files normally have the filename extension .gresource.xml. For a detailed description of the XML file format, see the GResource documentation.
-h, --help Print help and exit
--version Print program version and exit
--target=TARGET Store the compiled resources in the file TARGET. If not specified a filename based on the FILE basename is used.
--sourcedir=DIRECTORY The files referenced in FILE are loaded from this directory. If not specified, the current directory is used.
--generate Write the output file in the format selected for by its filename extension:
.c C source
.h C header
.gresource resource bundle
--generate-source Instead of a writing the resource bundle in binary form create a C source file that contains the resource bundle. This can then be compiled into an application for easy access.
--generate-header Generate a header file for use with C code generated by --generate-source.
--generate-dependencies Prints the list of files that the resource bundle references to standard output. This can be used to track dependencies in the build system. For example, the following make rule would mark test.gresource as depending on all the files that test.gresource.xml includes, so that is is automatically rebuilt if any of them change:
test.gresource: test.gresource.xml $(shell $(GLIB_COMPILE_RESOURCES) --generate-dependencies test.gresource.xml)
Note that this may or may not be portable to non-GNU make.
Also see --dependency-file.
--c-name Specify the prefix used for the C identifiers in the code generated by --generate-source and --generate-header.
--manual-register By default code generated by --generate-source uses automatic initialization of the resource. This works on most systems by using the compiler support for constructors. However, some (uncommon) compilers may not support this, you can then specify --manual-register, which will generate custom register and unregister functions that your code can manually call at initialization and uninitialization time.
--internal By default code generated by --generate-source declares all initialization functions as extern. So they are exported unless this is prevented by a link script or other means. Since libraries usually want to use the functions only internally it can be more useful to declare them as G_GNUC_INTERNAL which is what --internal does.
--external-data By default code generated by --generate-source embeds the resource data as a string literal. When --external-data is given, the data is only declared in the generated C file, and the data has to be linked externally.
--dependency-file=FILE Write dependencies in the same style as gcc -M -MF to the given file. If FILE is -, the dependencies are written to the standard output. Unlike --generate-dependencies, this option can be combined with other --generate options to generate dependencies as a side-effect of generating sources.
--generate-phony-targets When creating a dependency file with --dependency-file include phony targets in the same style as gcc -MP. This would typically be used with make.
XMLLINT The full path to the xmllint executable. This is used to preprocess resources with the xml-stripblanks preprocessing option. If this environment variable is not set, xmllint is searched for in the PATH.
GDK_PIXBUF_PIXDATA Deprecated since gdk-pixbuf 2.32, as GResource supports embedding modern image formats without conversion.
The full path to the gdk-pixbuf-pixdata executable. This is used to preprocess resources with the to-pixdata preprocessing option. If this environment variable is not set, gdk-pixbuf-pixdata is searched for in the PATH.
JSON_GLIB_FORMAT The full path to the json-glib-format executable. This is used to preprocess resources with the json-stripblanks preprocessing option. If this environment variable is not set, json-glib-format is searched for in the PATH.
IPYTHON(1)                   General Commands Manual                  IPYTHON(1)
ipython - Tools for Interactive Computing in Python.
ipython [options] files...
ipython subcommand [options]...
An interactive Python shell with automatic history (input and output), dynamic object introspection, easier configuration, command completion, access to the system shell, integration with numerical and scientific computing tools, web notebook, Qt console, and more.
For more information on how to use IPython, see 'ipython --help', or 'ipython --help-all' for all available command‐line options.
IPYTHONDIR This is the location where IPython stores all its configuration files.  The default is $HOME/.ipython if IPYTHONDIR is not defined.
You can see the computed value of IPYTHONDIR with `ipython locate`.
IPython uses various configuration files stored in profiles within IPYTHONDIR.  To generate the default configuration files and start configuring IPython, do 'ipython profile create', and edit '*_config.py' files located in IPYTHONDIR/profile_default.
IPython is written by the IPython Development Team <https://github.com/ipython/ipython>.
POWERSTAT(8)                 System Manager's Manual                POWERSTAT(8)
powerstat - a tool to measure power consumption
powerstat [options] [delay [count]]
powerstat measures the power consumption of a computer that has a battery power source or supports the RAPL (Running Average Power Limit) interface.  The output is like vmstat but also shows power consumption statistics.  At the end of a run, powerstat will calculate the average, standard deviation, minimum, maximum and geometic mean of the gathered data.
Note that running powerstat as root will provide extra information about process fork(2), exec(2) and exit(2) activity.
powerstat options are as follow:
-a     enable all statistics gathering options, equivalent to -c, -f, -t and -H.
-b     redo a sample measurement if a system is busy, the default for busy is considered less than 98% CPU idle. The CPU idle threshold can be altered using the -i option.
-c     gather CPU C-state activity and show the % time and count in each C-state at the end of the run.
-d delay specify delay in seconds before starting, default is 180 seconds when running on battery or 0 seconds when using RAPL. This gives the machine time to settle down and for the battery readings to stabilize.
-D     enable extra power stats showing all the power domain power readings. This currently only applies to the -R RAPL option.
-f     compute an average frequency from all on-line CPU cores. Unfortunately a CPU core is always active to gather any form of stats because powerstat has to be running to do so, so these statistics are skewed by this.  It is best to use this option with a reasonably large delay (more than 5 seconds) between samples to reduce the overhead of powerstat.
-g     show GPU power readings. Currently just Intel i915 is supported and one needs to run powerstat with root privilege to access the kernel i915 /sys debug interface.
-h     show help.
-H     show histogram of power measurements.
-i threshold specify the idle threshold (in % CPU idle) to force a re-sample measurement if the CPU is less idle than this level. This option implicitly enables the -b option.
-n     no headings. Column headings are printed when they scroll off the terminal; this option disables this and allows one to capture the output and parse the data without the need to filter out the headings.
-p     redo a sample measurement if any processes fork(), exec() or exit().
-r     redo if system is not idle and any processes fork(), exec() or exit(), an alias for -p -b.
-R     read power statistics from the RAPL (Running Average Power Limit) domains. This is supported by recent Linux kernels and Sandybridge and later Intel processors.  This only covers some of the hardware in the machine, such as the processor package, DRAM controller, CPU core (power plane 0), graphics uncore (power plane 1) and so forth, so the readings do not cover the entire machine. Because the  RAPL readings are accurate and available immediately, the start delay (-d option) is defaulted to zero seconds.
-s     this dumps a log of the process fork(), exec() and exit() activity on completion.