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.
 
 
 
 
 
 
Shawn O. Pearce ea09ea22d6 Don't allow contrib/workdir/git-new-workdir to trash existing dirs 18 years ago
..
blameview War on whitespace 18 years ago
completion Teach bash about completing arguments for git-tag 18 years ago
continuous contrib/continuous: a continuous integration build manager 18 years ago
emacs git.el: Added colors for dark background 18 years ago
examples Make verify-tag a builtin. 18 years ago
fast-import git-p4: Fix warnings about non-existant refs/remotes/p4/HEAD ref when running git-p4 sync the first time after a git clone. 18 years ago
gitview gitview: run blame with -C -C 18 years ago
hg-to-git
hooks Use the empty tree for base diff in paranoid-update on new branches 18 years ago
p4import Demote git-p4import to contrib status. 18 years ago
patches INSTALL: add warning on docbook-xsl 1.72 and 1.73 18 years ago
stats Add contrib/stats/mailmap.pl script 18 years ago
vim
workdir Don't allow contrib/workdir/git-new-workdir to trash existing dirs 18 years ago
README War on whitespace 18 years ago
remotes2config.sh Rewrite "git-frotz" to "git frotz" 18 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