Robert Karszniewicz 4209e4ca97 git-completion.bash: stash-show: complete $__git_diff_common_options 4 years ago
..
buildsystems f2f1250c47 cmake (Windows): recommend using Visual Studio's built-in CMake support 4 years ago
coccinelle c49c82aa4c commit: move members graph_pos, generation to a slab 5 years ago
completion 4209e4ca97 git-completion.bash: stash-show: complete $__git_diff_common_options 4 years ago
contacts 09ac673788 git-contacts: also recognise "Reported-by:" 8 years ago
credential 6579d93a97 contrib/credential/netrc: work outside a repo 5 years ago
diff-highlight 579789dbce diff-highlight: correctly match blank lines for flush 4 years ago
emacs 6d5ed4836d git{,-blame}.el: remove old bitrotting Emacs code 7 years ago
examples 49eb8d39c7 Remove contrib/examples/* 7 years ago
fast-import c839fcff65 import-tars: ignore the global PAX header 5 years ago
git-jump 240cf2a257 contrib/git-jump/git-jump: jump to exact location 7 years ago
git-shell-commands 54baefda8c Add sample commands for git-shell 15 years ago
hg-to-git d17ae00c97 hg-to-git: make it compatible with both python3 and python2 5 years ago
hooks ae821ffe83 multimail: fix a few simple spelling errors 5 years ago
long-running-filter c6b0831c9c docs: warn about possible '=' in clean/smudge filter process values 8 years ago
mw-to-git 9a8606465e remote-mediawiki: use "sh" to eliminate unquoted commands 4 years ago
persistent-https 2c9a2ae285 docs/config: mention protocol implications of url.insteadOf 8 years ago
remote-helpers b8686c661d contrib: git-remote-{bzr,hg} placeholders don't need Python 8 years ago
stats 53474eb92f contrib: update stats/mailmap script 12 years ago
subtree 8923a45f14 Merge branch 'dl/subtree-docs' 4 years ago
thunderbird-patch-inline 57eb1bef7d contrib/thunderbird-patch-inline/appp.sh: use the $( ... ) construct for command substitution 9 years ago
update-unicode e233bef43e unicode_width.h: rename to use dash in file name 7 years ago
vscode 12861e200a vscode: let cSpell work on commit messages, too 7 years ago
workdir bee286f8f7 git-new-workdir: mark script as LF-only 8 years ago
README a6080a0a44 War on whitespace 18 years ago
coverage-diff.sh 783faedd65 contrib: add coverage-diff script 6 years ago
git-resurrect.sh 3c833cae44 Merge branch 'jc/bs-t-is-not-a-tab-for-sed' 8 years ago
remotes2config.sh afa75bc8aa contrib: Make remotes2config.sh script more robust 17 years ago
rerere-train.sh ad53bf79aa contrib/rerere-train: optionally overwrite existing resolutions 8 years ago

README

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 that 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 are some general interests (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