Git Source Code Mirror - This is a publish-only repository and all pull requests are ignored. Please follow Documentation/SubmittingPatches procedure for any of your improvements. https://git-scm.com/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Junio C Hamano 657c7403a3 Merge branch 'ab/leak-check' 6 days ago
..
buildsystems cmake: support local installations of git 3 weeks ago
coccinelle Merge branch 'rs/cocci-array-copy' 1 month ago
completion git-prompt: fix expansion of branch colour codes 2 months ago
contacts git-contacts: also recognise "Reported-by:" 5 years ago
credential Merge branch 'ab/leak-check' 6 days ago
diff-highlight diff-highlight: correctly match blank lines for flush 2 years ago
emacs git{,-blame}.el: remove old bitrotting Emacs code 4 years ago
examples Merge branch 'bw/c-plus-plus' into ds/lazy-load-trees 4 years ago
fast-import import-tars: ignore the global PAX header 2 years ago
git-jump git-jump: pass "merge" arguments to ls-files 9 months ago
git-shell-commands Add sample commands for git-shell 12 years ago
hg-to-git hg-to-git: make it compatible with both python3 and python2 3 years ago
hooks multimail: stop shipping a copy 1 year ago
long-running-filter docs: warn about possible '=' in clean/smudge filter process values 6 years ago
mw-to-git t6000-t9999: detect and signal failure within loop 8 months ago
persistent-https docs/config: mention protocol implications of url.insteadOf 5 years ago
remote-helpers contrib: git-remote-{bzr,hg} placeholders don't need Python 6 years ago
scalar Merge branch 'ab/leak-check' 6 days ago
stats contrib: update stats/mailmap script 10 years ago
subtree t/Makefile: don't remove test-results in "clean-except-prove-cache" 3 weeks ago
thunderbird-patch-inline contrib/thunderbird-patch-inline/appp.sh: use the $( ... ) construct for command substitution 7 years ago
update-unicode unicode_width.h: rename to use dash in file name 4 years ago
vscode vscode: improve tab size and wrapping 2 months ago
workdir git-new-workdir: mark script as LF-only 5 years ago
README War on whitespace 15 years ago
coverage-diff.sh contrib: add coverage-diff script 4 years ago
git-resurrect.sh contrib/git-resurrect.sh: use hash-agnostic OID pattern 2 years ago
remotes2config.sh contrib: Make remotes2config.sh script more robust 15 years ago
rerere-train.sh contrib/rerere-train: avoid useless gpg sign in training 1 month 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