Initial commit

5 files changed, 1251 insertions, 0 deletions

diff --git a/macros/latex/contrib/latexgit/LICENSE b/macros/latex/contrib/latexgit/LICENSE
new file mode 100644
index 0000000000..9cecc1d466
--- /dev/null
+++ b/macros/latex/contrib/latexgit/LICENSE
@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    {one line to give the program's name and a brief idea of what it does.}
+    Copyright (C) {year}  {name of author}
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    {project}  Copyright (C) {year}  {fullname}
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.
diff --git a/macros/latex/contrib/latexgit/README.md b/macros/latex/contrib/latexgit/README.md
new file mode 100644
index 0000000000..3cd85a0da0
--- /dev/null
+++ b/macros/latex/contrib/latexgit/README.md
@@ -0,0 +1,14 @@
+# latexgit
+LaTeX git wrapper
+
+This package is on [CTAN][ctan].
+
+Several macros are defined to fetch git information and typeset it. The macros
+defined by LaTeXgit can be helpful to documentation authors and others to whom
+clear document versioning is important.
+
+Copyright &copy; 2016 [Camil Staps][camilstaps]. Licensed under
+GPL v3, see the LICENSE file for more details.
+
+[ctan]: http://www.ctan.org/pkg/latexgit
+[camilstaps]: https://camilstaps.nl
diff --git a/macros/latex/contrib/latexgit/latexgit.dtx b/macros/latex/contrib/latexgit/latexgit.dtx
new file mode 100644
index 0000000000..df840b5e1f
--- /dev/null
+++ b/macros/latex/contrib/latexgit/latexgit.dtx
@@ -0,0 +1,534 @@
+% \iffalse vim: expandtab:
+% \fi
+% \iffalse meta-comment
+%<*internal>
+\def\nameofplainTeX{plain}
+\ifx\fmtname\nameofplainTex\else
+  \expandafter\begingroup
+\fi
+%</internal>
+%<*install>
+\input docstrip.tex
+\keepsilent
+\askforoverwritefalse
+\preamble
+latexgit
+Author: Camil Staps <info@camilstaps.nl>
+\endpreamble
+\postamble
+Copyright (c) 2016 Camil Staps <info@camilstaps.nl>
+Licensed under GPL v3.
+\endpostamble
+\usedir{tex/latex/latexgit}
+\generate{
+  \file{\jobname.sty}{\from{\jobname.dtx}{package}}
+}
+%</install>
+%<install>\endbatchfile
+%<*internal>
+\usedir{source/latex/latexgit}
+\generate{
+    \file{\jobname.ins}{\from{\jobname.dtx}{install}}
+}
+\nopreamble\nopostamble
+\ifx\fmtname\nameofplainTeX
+  \expandafter\endbatchfile
+\else
+  \expandafter\endgroup
+\fi
+%</internal>
+%<*driver>
+\documentclass{ltxdoc}
+\usepackage[T1]{fontenc}
+\usepackage{lmodern}
+\usepackage{\jobname}
+\usepackage[numbered]{hypdoc}
+\usepackage{showexpl}
+\usepackage{xcolor}
+\lstset{%
+    basicstyle=\ttfamily\small,
+    commentstyle=\itshape\ttfamily\small,
+    showspaces=false,
+    keepspaces=true,
+    showstringspaces=false,
+    breaklines=true,
+    backgroundcolor=\color{lightgray},
+    breakautoindent=true,
+}
+\usepackage{enumitem}
+\usepackage{verbatim}
+\usepackage{amssymb}
+\EnableCrossrefs
+\CodelineIndex
+\RecordChanges
+\setcounter{IndexColumns}2
+\newlist{options}{description}{1}
+\setlist[options]{font=\small\texttt,itemsep=0pt,style=nextline}
+\newcommand{\git}[0]{\gitcmd{git}}
+\newcommand{\gitcmd}[1]{\texttt{\small#1}}
+\newcommand{\gitopt}[1]{%
+  \texttt{\small\hyperref[options]{\textcolor{black}{#1}}}%
+}
+\newcommand{\bashcmd}[1]{\texttt{\small#1}}
+\newcommand{\texcmd}[1]{\texttt{\small#1}}
+\def\GitOptions#1,#2\relax{%
+  \gitopt{#1}%
+  \begingroup%
+  \ifx\relax#2\relax %
+    \def\next{\endgroup}%
+  \else%
+    \def\next{, \endgroup\GitOptions#2\relax}%
+  \fi%
+  \next%
+}
+\def\gitoptions#1{%
+  Recognised options:
+  \begingroup%
+  \edef\@tempa{#1,}%
+  \expandafter\endgroup%
+  \expandafter\GitOptions\@tempa\relax%
+  \unskip.
+}
+\begin{document}
+  \DocInput{\jobname.dtx}
+  \newpage
+  \PrintChanges
+  \newpage
+  \PrintIndex
+\end{document}
+%</driver>
+% \fi
+%
+%\GetFileInfo{\jobname.sty}
+%
+%\title{The \latexgit{} package}
+%\author{Camil Staps\thanks{Email: info@camilstaps.nl}}
+%\date{^^A
+%  Version \gitcommithash[shortHash]\\
+%  \small{\gitcommitdate[formatDate,formatTime,formatInterDateTime={,~},showTimeZone]}}
+%
+%\maketitle
+%
+%\gitchanges
+%
+%\DoNotIndex{\def,\edef,\expandafter,\global,\let,\newcommand,\relax,\catcode}
+%\DoNotIndex{\begingroup,\endgroup}
+%\expandafter\DoNotIndex\expandafter{\string\^}
+%\DoNotIndex{\hbox,\ifdim,\setbox,\wd}
+%\DoNotIndex{\ifeof,\else,\fi,\newif}
+%\DoNotIndex{\NeedsTeXFormat,\PackageError,\ProvidesPackage,\RequirePackage}
+%\DoNotIndex{\endlinechar,\newread,\openin,\read,\readline}
+%\DoNotIndex{\space,\unskip}
+%\DoNotIndex{\LaTeX,\pgfkeys,\changes}
+%\DoNotIndex{\formatdate,\formattime}
+%\DoNotIndex{\git@@revision,\git@@thisdate,\git@@thishash,\git@@thismsg,\git@@parent}
+%
+%\begin{abstract}
+%  This is the documentation of the \latexgit{} package.
+%  Several macros are defined to fetch \git{} information and typeset it.
+%  The macros defined by \latexgit{} can be helpful to documentation authors
+%  and others to whom clear document versioning is important.
+%\end{abstract}
+%
+%\tableofcontents
+%
+%\section{Overview}
+%\label{sec:overview}
+%\subsection{Related packages}
+%\label{sec:overview:related-packages}
+%Brent Longborough's \textsf{gitinfo} and \textsf{gitinfo2} packages have
+%similar features, with a different interface. Instead of running \git{}
+%commands, it relies on special \git{} files. This has the advantage that it
+%works on Windows, however, \git{} hooks have to be put into place.
+%
+%Andr\'e Hilbig's \textsf{gitfile-info} does something similar as
+%\textsf{gitinfo} and \latexgit, but the package manual is in German so who
+%knows. It seems that Python and \git{} hooks are required.
+%
+%\subsection{Dependencies}
+%\label{sec:overview:dependencies}
+%\latexgit{} gets its information by running \git{} commands. It uses
+%\cs{write18} for this, so documents using \latexgit{} will have to be compiled
+%with the \bashcmd{-shell-escape} flag.
+%
+%Most of the information is retrieved using \git{} but then parsed using
+%\bashcmd{grep}, \bashcmd{cut} and similar tools. Unfortunately, this is
+%necessary: \gitcmd{git log} accepts arbitrary formats, but uses the percent
+%sign in these formats, and running commands with percent signs does not seem
+%possible using \cs{write18}.
+%
+%An unfortunate side effect of this is that this package will not work on
+%Windows.
+%
+%\subsection{Getting information}
+%\label{sec:overview:getting-information}
+%\latexgit{} runs a shell command using \cs{git@command}. This macro reads the
+%result into \cs{git@rawresult.} This result contains a newline character at
+%the end that needs to be removed to avoid unwanted spacing. Therefore,
+%\cs{git@result} is defined as a wrapper for \cs{git@rawresult} that removes
+%this spacing with \cs{unskip}.
+%
+%\subsection{Interface}
+%For each information-fetching command, two versions are defined: one, which
+%only executes the command (leaving the result available in \cs{git@result});
+%and one, which executes the command and writes the result. An example is
+%\cs{git@commithash} with its counterpart \cs{gitcommithash}. Usually, the
+%latter is most useful.
+%
+%\section{Options}
+%\label{sec:options}
+%A number of options is available to all macros that fetch information through
+%a \textsf{pgfkeys} interface. All keys are recognised by all macros, but not
+%all are considered by each macro. Check the documentation for specific macros
+%to see which options are relevant.
+%
+%\begin{options}
+%  \label{options}
+%  \item[directory=DIR]
+%    Use the git repository in directory \verb$DIR$ (or its first parent
+%    directory that is a git repository). \latexgit{} will \bashcmd{cd} to this
+%    directory before executing the actual \git{} command.
+%  \item[formatDate]
+%    Format dates using \textsf{datetime}'s \cs{formatdate}.
+%  \item[formatTime]
+%    Format times using \textsf{datetime}'s \cs{formattime}.
+%  \item[formatInterDateTime]
+%    If both \gitopt{formatDate} and \gitopt{formatTime} are set, this is put
+%    in between (e.g.  `\verb$\space{}at\space{}$' in English --- this is also
+%    the default).
+%  \item[revision=REV]
+%    Get the hash of revision \verb$REV$ (e.g.  \gitcmd{master},
+%    \gitcmd{HEAD\textasciicircum}, etc.). Note that if multiple circumflexes
+%    are desired, the catcode of \verb$^$ has to be changed. For example:
+%    \LTXinputExample[numbers=none,pos=r]{exmp/catcode-circumflex.tex}
+%  \item[showTimeZone]
+%    When \gitopt{formatTime} is set: show the time zone between parentheses
+%    after the time.
+%  \item[shortHash]
+%    Get only the first seven characters of the hash, as in \gitcmd{git log
+%    -{}-oneline}.
+%\end{options}
+%
+%\section{Examples}
+%\label{sec:examples}
+%\DescribeMacro{\gitcommithash}
+%\DescribeMacro{\gitcommitmsg}
+%\DescribeMacro{\gitcommitauthor}
+%\DescribeMacro{\gitcommitauthorname}
+%\DescribeMacro{\gitcommitauthoremail}
+%    These macros are used to get and print basic commit information.
+%    \LTXinputExample[pos=b,numbers=none]{exmp/gitcommit.tex}
+%
+%\DescribeMacro{\gitcommitdate}
+%    This macro displays the \git{} commit date.
+%    The following example shows a usage example and shows the results of the
+%    options
+%    \gitopt{formatDate}, \gitopt{formatTime} and \gitopt{showTimeZone}.
+%    \LTXinputExample[pos=b,numbers=none]{exmp/gitcommitdate.tex}
+%
+%\section{Implementation}
+%\label{sec:implementation}
+%Define the package and load required packages.
+%
+%    \begin{comment}
+%<*package>
+%    \end{comment}
+%    \begin{macrocode}
+\NeedsTeXFormat{LaTeX2e}
+\ProvidesPackage{latexgit}[2016/08/24]
+
+\RequirePackage{pgfkeys}
+\RequirePackage{datetime}
+%    \end{macrocode}
+%
+%\begin{macro}{\latexgit}
+%    Prints the name of the package.
+%    \begin{macrocode}
+\newcommand{\latexgit}[0]{\LaTeX{}git}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\git@result}
+%    When a \git{} command is run, the result is stored in \cs{git@rawresult}.
+%    However, using \cs{read} results in spacing at the end of the macro.
+%    Hence, we need to use \cs{unskip} to remove this spacing.
+%    This is a wrapper for \cs{git@rawresult} that adds this \cs{unskip}.
+%    \begin{macrocode}
+\newcommand{\git@result}[0]{\git@rawresult\unskip}
+%    \end{macrocode}
+%\end{macro}
+%
+%    We now define the keys accepted by git macros. The following options are
+%    recognised. Check the documentation of the macro to see which options are
+%    considered.
+%
+%    \begin{macrocode}
+\newif\ifgit@opt@FormatDate
+\newif\ifgit@opt@FormatTime
+\newif\ifgit@opt@ShortHash
+\newif\ifgit@opt@ShowTimeZone
+\pgfkeys{
+  /git/.is family, /git,
+  default/.style={
+    directory=.,
+    formatDate=false,
+    formatInterDateTime=\space{}at\space{},
+    formatTime=false,
+    revision=HEAD,
+    showTimeZone=false,
+    shortHash=true,
+  },
+  directory/.estore in=\git@opt@Directory,
+  formatDate/.is if=git@opt@FormatDate,
+  formatInterDateTime/.estore in=\git@opt@FormatInterDateTime,
+  formatTime/.is if=git@opt@FormatTime,
+  revision/.estore in=\git@opt@Revision,
+  showTimeZone/.is if=git@opt@ShowTimeZone,
+  shortHash/.is if=git@opt@ShortHash,
+}
+%    \end{macrocode}
+%
+%\begin{macro}{\git@command}
+%    Run a \git{} command and read the output into \cs{git@rawresult}. Before
+%    running the command, the directory will change to \cs{git@opt@Directory}.
+%    \begin{macrocode}
+\newread\git@stream%
+\newcommand{\git@command}[1]{%
+  \def\git@rawresult{}%
+  \openin\git@stream|"cd \git@opt@Directory; #1"
+  \ifeof\git@stream%
+    \PackageError{latexgit}%
+      {invoke LaTeX with the -shell-escape flag}%
+      {invoke LaTeX with the -shell-escape flag}%
+  \else%
+    \begingroup%
+    \catcode`\^^M9%
+    \endlinechar=-1%
+    \readline\git@stream to \git@streamoutput%
+    \global\let\git@rawresult\git@streamoutput%
+    \endgroup%
+  \fi%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\gitcommithash}
+%    Get a commit hash.
+%    \gitoptions{directory,revision,shortHash}
+%
+%    \begin{macrocode}
+\newcommand{\gitcommithash}[1][]{%
+  \git@commithash[#1]\git@result}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\git@commithash}
+%    Like \cs{gitcommithash}, but does not return the output.
+%    \begin{macrocode}
+\newcommand{\git@commithash}[1][]{%
+  \pgfkeys{/git,default,#1}%
+  \ifgit@opt@ShortHash%
+    \git@command{git log -n 1 --oneline \git@opt@Revision
+      | cut -d' ' -f1}%
+  \else%
+    \git@command{git log -n 1 \git@opt@Revision
+      | head -1 | cut -d' ' -f2}%
+  \fi%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\gitcommitmsg}
+%    Get a commit message.
+%    \gitoptions{directory,revision}
+%
+%    \begin{macrocode}
+\newcommand{\gitcommitmsg}[1][]{%
+  \git@commitmsg[#1]\git@result}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\git@commitmsg}
+%    Like \cs{gitcommitmsg}, but does not return the output.
+%    \begin{macrocode}
+\newcommand{\git@commitmsg}[1][]{%
+  \pgfkeys{/git,default,#1}%
+  \git@command{git log -n 1 --oneline \git@opt@Revision
+    | cut -d' ' -f2-}%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\git@formatCommitDate}
+%    Format a commit date in ISO format using \textsf{datetime}'s
+%    \cs{formatdate}.
+%    \begin{macrocode}
+\def\git@formatCommitDate#1-#2-#3 #4:#5:#6 +#7\relax{%
+  \formatdate{#3}{#2}{#1}%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\git@formatCommitTime}
+%    Format a commit time using \textsf{datetime}'s \cs{formattime}.
+%    \gitoptions{showTimeZone}
+%    \begin{macrocode}
+\def\git@formatCommitTime#1-#2-#3 #4:#5:#6 +#7\relax{%
+  \formattime{#4}{#5}{#6}%
+  \ifgit@opt@ShowTimeZone%
+    \space(+#7\unskip)%
+  \fi%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\gitcommitdate}
+%    Get a commit date. If \gitopt{formatDate} is set,
+%    \cs{git@formatCommitDate} will be used. If \gitopt{formatTime} is set, and
+%    \gitopt{formatDate} is unset, \cs{git@formatCommitTime} will be used.
+%    \gitoptions{directory,formatDate,formatTime,revision,showTimeZone}
+%
+%    \begin{macrocode}
+\newcommand{\gitcommitdate}[1][]{%
+  \git@commitdate[#1]%
+  \ifgit@opt@FormatDate%
+    \expandafter\git@formatCommitDate\git@rawresult\relax%
+    \ifgit@opt@FormatTime%
+      \git@opt@FormatInterDateTime%
+      \expandafter\git@formatCommitTime\git@rawresult\relax%
+    \fi
+  \else\ifgit@opt@FormatTime%
+    \expandafter\git@formatCommitTime\git@rawresult\relax%
+  \else
+    \git@result%
+  \fi\fi%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\git@commitdate}
+%    Like \cs{gitcommitdate}, but does not return the output.
+%    \begin{macrocode}
+\newcommand{\git@commitdate}[1][]{%
+  \pgfkeys{/git,default,#1}%
+  \git@command{git log -n 1 --date=iso \git@opt@Revision
+    | grep Date | head -1 | cut -d' ' -f2-}%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\gitcommitauthor}
+%    Get a commit author.
+%    \gitoptions{directory,revision}
+%
+%    \begin{macrocode}
+\newcommand{\gitcommitauthor}[1][]{%
+  \git@commitauthor[#1]\git@result}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\git@commitauthor}
+%    Like \cs{gitcommitauthor}, but does not return the output.
+%    \begin{macrocode}
+\newcommand{\git@commitauthor}[1][]{%
+  \pgfkeys{/git,default,#1}%
+  \git@command{git log -n 1 \git@opt@Revision
+    | grep Author | head -1 | cut -d' ' -f2-}%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\gitcommitauthorname}
+%    Get a commit author's name.
+%    \gitoptions{directory,revision}
+%
+%    \begin{macrocode}
+\newcommand{\gitcommitauthorname}[1][]{%
+  \git@commitauthorname[#1]\git@result}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\git@commitauthorname}
+%    Like \cs{gitcommitauthorname}, but does not return the output.
+%    \begin{macrocode}
+\newcommand{\git@commitauthorname}[1][]{%
+  \pgfkeys{/git,default,#1}%
+  \git@command{git log -n 1 \git@opt@Revision
+    | grep Author | head -1 | cut -d' ' -f2- | cut -d'<' -f1}%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\gitcommitauthoremail}
+%    Get a commit author's email address.
+%    \gitoptions{directory,revision}
+%
+%    \begin{macrocode}
+\newcommand{\gitcommitauthoremail}[1][]{%
+  \git@commitauthoremail[#1]\git@result}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\git@commitauthoremail}
+%    Like \cs{gitcommitauthoremail}, but does not return the output.
+%    \begin{macrocode}
+\newcommand{\git@commitauthoremail}[1][]{%
+  \pgfkeys{/git,default,#1}%
+  \git@command{git log -n 1 \git@opt@Revision
+    | grep Author | head -1 | cut -d' ' -f2-
+    | cut -d'<' -f2 | cut -d'>' -f1}%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\git@commitparent}
+%    Get the hash of the first parent.
+%    \begin{macrocode}
+\newcommand{\git@commitparent}[1][]{%
+  \pgfkeys{/git,default,#1}%
+  \git@command{git log -n 1 --pretty=raw \git@opt@Revision
+    | grep parent | head -1 | cut -d' ' -f2}%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\gitchanges}
+%    Record the full \git{} commit history (following first parents using
+%    \cs{git@commitparent}) using \cs{changes}.
+%    \begin{macrocode}
+\newcommand{\gitchanges}[1][]{%
+  \git@changes[#1]{HEAD}
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%\begin{macro}{\git@changes}
+%    Like \cs{gitchanges}, but accepts an extra argument for the revision.
+%    \begin{macrocode}
+\newcommand{\git@changes}[2][]{%
+  \edef\git@@revision{#2}%
+  \git@commithash[revision=\git@@revision]%
+  \edef\git@@thishash{\git@rawresult}%
+  \git@command{git log -n 1 --date=iso \git@@revision
+    | grep Date | head -1 | cut -d' ' -f4}%
+  \edef\git@@thisdate{\git@rawresult}%
+  \git@commitmsg[revision=\git@@revision]%
+  \edef\git@@thismsg{\git@rawresult}%
+  \changes{\git@@thisdate\unskip: \git@@thishash}\git@@thisdate\git@@thismsg%
+  \git@commitparent[revision=\git@@revision]%
+  \let\git@@parent\git@rawresult%
+  \setbox0=\hbox{\git@@parent\unskip}\ifdim\wd0=0pt
+  \else%
+    \git@changes{\git@@parent}%
+  \fi%
+}
+%    \end{macrocode}
+%\end{macro}
+%
+%
+%    \begin{comment}
+%</package>
+%    \end{comment}
+%
+%\Finale
+\endinput
diff --git a/macros/latex/contrib/latexgit/latexgit.ins b/macros/latex/contrib/latexgit/latexgit.ins
new file mode 100644
index 0000000000..532ab7ac2d
--- /dev/null
+++ b/macros/latex/contrib/latexgit/latexgit.ins
@@ -0,0 +1,29 @@
+%%
+%% This is file `latexgit.ins',
+%% generated with the docstrip utility.
+%%
+%% The original source files were:
+%%
+%% latexgit.dtx  (with options: `install')
+%% latexgit
+%% Author: Camil Staps <info@camilstaps.nl>
+\input docstrip.tex
+\keepsilent
+\askforoverwritefalse
+\preamble
+latexgit
+Author: Camil Staps <info@camilstaps.nl>
+\endpreamble
+\postamble
+Copyright (c) 2016 Camil Staps <info@camilstaps.nl>
+Licensed under GPL v3.
+\endpostamble
+\usedir{tex/latex/latexgit}
+\generate{
+  \file{\jobname.sty}{\from{\jobname.dtx}{package}}
+}
+\endbatchfile
+%% Copyright (c) 2016 Camil Staps <info@camilstaps.nl>
+%% Licensed under GPL v3.
+%%
+%% End of file `latexgit.ins'.
diff --git a/macros/latex/contrib/latexgit/latexgit.pdf b/macros/latex/contrib/latexgit/latexgit.pdf
new file mode 100644
index 0000000000..5ddb54d567
--- /dev/null
+++ b/macros/latex/contrib/latexgit/latexgit.pdf