Skip to content

Files

Latest commit

a4af0b6 · Feb 12, 2025

History

History
This branch is 1 commit ahead of, 1031 commits behind git/git:master.

contrib

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Feb 3, 2025
May 7, 2024
Jan 21, 2025
Jul 27, 2017
Aug 14, 2024
Oct 23, 2024
Apr 16, 2018
Mar 26, 2018
Mar 24, 2020
Sep 23, 2024
Aug 12, 2010
Jun 11, 2021
Jan 29, 2025
Jan 29, 2025
Dec 6, 2016
Oct 23, 2024
Jun 1, 2017
Mar 3, 2017
Dec 12, 2012
Jan 17, 2025
Dec 27, 2015
Apr 11, 2018
Apr 5, 2024
Feb 7, 2024
Oct 5, 2023
Mar 16, 2024
Oct 8, 2020
Jan 17, 2025
Dec 4, 2007
Jul 19, 2022
Contributed Software

Although these pieces are available as part of the official git
source tree, they are in somewhat different status.  The
intention is to keep interesting tools around git here, maybe
even experimental ones, to give users an easier access to them,
and to give tools wider exposure, so that they can be improved
faster.

I am not expecting to touch these myself that much.  As far as
my day-to-day operation is concerned, these subdirectories are
owned by their respective primary authors.  I am willing to help
if users of these components and the contrib/ subtree "owners"
have technical/design issues to resolve, but the initiative to
fix and/or enhance things _must_ be on the side of the subtree
owners.  IOW, I won't be actively looking for bugs and rooms for
enhancements in them as the git maintainer -- I may only do so
just as one of the users when I want to scratch my own itch.  If
you have patches to things in contrib/ area, the patch should be
first sent to the primary author, and then the primary author
should ack and forward it to me (git pull request is nicer).
This is the same way as how I have been treating gitk, and to a
lesser degree various foreign SCM interfaces, so you know the
drill.

I expect things that start their life in the contrib/ area
to graduate out of contrib/ once they mature, either by becoming
projects on their own, or moving to the toplevel directory.  On
the other hand, I expect I'll be proposing removal of disused
and inactive ones from time to time.

If you have new things to add to this area, please first propose
it on the git mailing list, and after a list discussion proves
there is general interest (it does not have to be a
list-wide consensus for a tool targeted to a relatively narrow
audience -- for example I do not work with projects whose
upstream is svn, so I have no use for git-svn myself, but it is
of general interest for people who need to interoperate with SVN
repositories in a way git-svn works better than git-svnimport),
submit a patch to create a subdirectory of contrib/ and put your
stuff there.

-jc