gitster Merge branch 'sb/cocci-pending'
A coding convention around the Coccinelle semantic patches to have
two classes to ease code migration process has been proposed and
its support has been added to the Makefile.

* sb/cocci-pending:
  coccicheck: introduce 'pending' semantic patches
Latest commit 0722553 Nov 19, 2018
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
buildsystems mark Windows build scripts executable Nov 25, 2013
coccinelle coccicheck: introduce 'pending' semantic patches Nov 14, 2018
completion Merge branch 'nd/complete-format-patch' Nov 13, 2018
contacts git-contacts: also recognise "Reported-by:" Jul 27, 2017
credential mingw: load system libraries the recommended way Oct 24, 2018
diff-highlight diff-highlight: detect --graph by indent Mar 21, 2018
emacs git{,-blame}.el: remove old bitrotting Emacs code Apr 16, 2018
examples Remove contrib/examples/* Mar 26, 2018
fast-import import-tars: read overlong names from pax extended header May 23, 2018
git-jump contrib/git-jump/git-jump: jump to exact location Jun 22, 2018
git-shell-commands Add sample commands for git-shell Aug 12, 2010
hg-to-git Replace Free Software Foundation address in license notices Nov 9, 2017
hooks hooks/pre-auto-gc-battery: allow gc to run on non-laptops Feb 28, 2018
long-running-filter docs: warn about possible '=' in clean/smudge filter process values Dec 6, 2016
mw-to-git mw-to-git/t9360: fix broken &&-chain Jul 31, 2018
persistent-https docs/config: mention protocol implications of url.insteadOf Jun 1, 2017
remote-helpers contrib: git-remote-{bzr,hg} placeholders don't need Python Mar 3, 2017
stats contrib: update stats/mailmap script Dec 12, 2012
subtree Merge branch 'ch/subtree-build' Oct 30, 2018
svn-fe contrib/svn-fe: fix Makefile Aug 28, 2014
thunderbird-patch-inline contrib/thunderbird-patch-inline/appp.sh: use the $( ... ) construct … Dec 27, 2015
update-unicode unicode_width.h: rename to use dash in file name Apr 11, 2018
vscode vscode: let cSpell work on commit messages, too Jul 30, 2018
workdir git-new-workdir: mark script as LF-only May 10, 2017
README War on whitespace Jun 7, 2007
coverage-diff.sh contrib: add coverage-diff script Oct 10, 2018
git-resurrect.sh Merge branch 'jc/bs-t-is-not-a-tab-for-sed' Apr 17, 2017
remotes2config.sh contrib: Make remotes2config.sh script more robust Dec 4, 2007
rerere-train.sh contrib/rerere-train: optionally overwrite existing resolutions Jul 26, 2017

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