6baa57b5a0
This compensates for an selinux bug reported on #gitolite by John Hawley (warthog9). sh/bash uses a tempfile to do this, which in turn causes some problems in selinux; I really don't [need to] know more than that. *Technically* this is a bug in selinux/policy, and would qualify for an entry in "nagp"... but: (1) the changes are small and localised (2) the problem makes gitolite -- currently -- unusable with selinux, and what use is a security program which can't run under selinux (regardless of whose fault it is)? and finally (3) if I can't break my own rules for one of my most high-profile users then what's the point of owning the code? :-) ---- Implementation notes: I've only done this for code that is likely/meant to be used in production I also slip-streamed in a URL fix (from when I changed all the online document rendering) |
||
---|---|---|
conf | ||
contrib | ||
doc | ||
hooks | ||
src | ||
t | ||
.gitattributes | ||
.gitignore | ||
Makefile | ||
README.mkd |
Gitolite README
Github users: please read the "wiki" link at the top of the page before submitting issues or pull requests.
If you're really impatient, and you're familiar with Unix and ssh, follow the quick install instructions.
But if you want to do anything meaningful with gitolite you have to spend some time cuddling up to the docs. The complete online documentation starts here -- this is the best starting point for general questions about git, such as what it is, why you would need it, features, contact/mailing list info, and so on.
For convenience, here is a link to the master table of contents, which is very useful to search using your browser's search function.