aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix setting umask in setup_gitweb_access() and refactoringgitolite-gentoo-2.3.3master-g2Christian Ruppert2014-08-231-5/+2
| | | | Signed-off-by: Christian Ruppert <idl0r@gentoo.org>
* All calls to git-config need to be wrapped by the umask handler.Robin H. Johnson2014-08-231-0/+6
| | | | Signed-off-by: Robin H. Johnson <robbat2@orbis-terrarum.net>
* Only change umask after wildrepos check.Robin H. Johnson2014-08-231-2/+3
| | | | Signed-off-by: Robin H. Johnson <robbat2@orbis-terrarum.net>
* Do not assume that the test user is in a group of the same name.Robin H. Johnson2014-08-239-126/+127
| | | | Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
* Use BashChristian Ruppert2014-01-191-1/+1
|
* Add dist.shChristian Ruppert2014-01-191-0/+31
|
* Fix umask stability issues that caused only partially visible repos in gitweb.gitolite-gentoo-2.3.2Robin H. Johnson2013-11-051-3/+10
| | | | Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
* Merge branch 'upstream'v2.3.1-gentoogitolite-gentoo-2.3.1Christian Ruppert2012-05-2046-524/+1666
|\
| * v2.3.1v2.3.1upstream-g2Sitaram Chamarty2012-05-141-0/+5
| |
| * git-config should work even if description is set!Sitaram Chamarty2012-04-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the optimisation that I just broke here was responsible for a bug that ignores config entries if you also had a description there repo @all config foo.bar.testAAA = "testAAA" repo foo1 foo2 RW+ = u1 u2 R = gitweb foo1 "sitaram" = "some project" This is because the %git_configs hash has been wiped out earlier (when can_read($repo, "gitweb") was first called) yet now you're not giving it a chance to get filled because $desc short-circuits can_read. (incidentally, this is one of those things that makes g3 so nice in comparision, because I decided not to be so fixated on efficiency!)
| * next round of doc fixesSitaram Chamarty2012-03-251-2/+2
| |
| * mention g3 in READMESitaram Chamarty2012-03-251-0/+18
| |
| * mirroring: fix several minor issues related to 'reponame.git'Sitaram Chamarty2012-03-243-1/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - git prepends a '/' when people use the full form of an ssh URL. Since I *never* use those, (I prefer setting an ssh host alias and just saying 'git95:gitolite' for example), I never caught this. - people will also append a '.git'. It's supposed to work either way, but it wasn't. I had missed a few places where the user might send in 'reponame.git' and was implicitly assuming it would be 'reponame' - finally, we slip-streamed in a wrapper for system() Big thanks and kudos to Michael Brown for catching these issues, and (hopefully, heh!) testing my fixes ;-)
| * (oopsies!) minor bug in a hurriedly written one-linerSitaram Chamarty2012-03-201-1/+1
| | | | | | | | pretty bad "bug percentage per line of code" though!
| * allow "config hooks.emailprefox = '[%GL_REPO]'" and suchSitaram Chamarty2012-03-201-0/+1
| |
| * Be compatible with older versions of File::PathGreg Bacon2012-03-091-2/+2
| |
| * specify documentation licensing as CC-BY-NC-SASitaram Chamarty2012-03-022-2/+11
| |
| * replaced comm with grep for devices without commArno Gramatke2012-03-021-1/+1
| |
| * replaced mktemp with a perl equivalent to make the setup usable on machines ↵Arno Gramatke2012-03-021-1/+1
| | | | | | | | without mktemp.
| * fork ADC: stop carrying along non-gitolite hooksSitaram Chamarty2012-02-291-1/+9
| | | | | | | | | | | | When someone adds a repo-specific hook to their repo, then create a 'fork' via the fork ADC, this repo-specific hook also get carried across, but should not.
| * merge all the '-h' related changesSitaram Chamarty2012-02-297-9/+43
| |\ | | | | | | | | | | | | run through the main test suite, (which really only uses 2 of these programs), smoke tested the others, but not rigorously tested otherwise
| | * gl-conf-convert learns '-h'Sitaram Chamarty2012-02-291-0/+4
| | |
| | * gl-dryrun learns '-h', plus a couple of other fixesSitaram Chamarty2012-02-291-3/+5
| | |
| | * gl-admin-push learns '-h'Sitaram Chamarty2012-02-291-0/+9
| | |
| | * gl-mirror-shell learns '-h'Sitaram Chamarty2012-02-291-2/+5
| | |
| | * sshkeys-lint learns '-h'Sitaram Chamarty2012-02-291-2/+3
| | |
| | * gl-tool learns '-h'Sitaram Chamarty2012-02-271-1/+1
| | |
| | * gl-system-install learns '-h'Sitaram Chamarty2012-02-271-1/+16
| |/
| * gl-setup changes:Sitaram Chamarty2012-02-272-13/+92
| | | | | | | | | | | | - learns to not run sshkeys-lint when told to be extra quiet - gets its own little doc section (appendix d) - get a quick help with '-h'
| * (minor fixups related to virtual ref)Sitaram Chamarty2012-02-263-5/+3
| |
| * 3 new VREFs plus docSitaram Chamarty2012-02-267-206/+239
| | | | | | | | | | | | | | - 'dupkeys' -- catch duplicate keys in keydir - 'email-check' -- "you can only push your own commits" plus, 'merge-check' -- how we could have done the no-merges policy
| * vref: docsSitaram Chamarty2012-02-261-0/+222
| |
| * 'filetype' VREFSitaram Chamarty2012-02-264-1/+177
| |
| * vref: testsSitaram Chamarty2012-02-263-1/+154
| |
| * vref: codeSitaram Chamarty2012-02-263-27/+105
| | | | | | | | | | | | | | - compile: VREF/ is special, like NAME/ - update hook: use a new "check_vrefs" sub to - spawn helpers for each vref in @allowed_refs - for each vref returned by the helper, call check_ref
| * next round of doc changesSitaram Chamarty2012-02-248-10/+45
| |
| * <sigh> why won't people read just *one* para more...?Sitaram Chamarty2012-02-221-9/+9
| | | | | | | | | | | | OK I agree the starting line was *just* misleading enough to give the opposite impression, but still, when the next para starts with "The rules are..." wouldn't you expect people would read *that* too?
| * fix http install (broken by d08aca); add a quick smoke testSitaram Chamarty2012-02-224-1/+153
| |
| * add a standalone test for gl-system-installSitaram Chamarty2012-02-221-0/+178
| |
| * clean up gl-system-installSitaram Chamarty2012-02-222-97/+109
| | | | | | | | | | | | | | | | - redo it in perl - make it flow easier, with all the cruft in subs and overall, make it obvious that this program does for a manual install what doc/packaging.mkd advices packagers to do.
| * clean up gl-installSitaram Chamarty2012-02-222-78/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - move wrap_mkdir() to gitolite.pm - remove junk left over from days when dinosaurs ruled the world - reuse setup_environment() from gitolite.pm instead of rolling our own code for PATH and umask part of it's function (the rest is harmless) - and most important, remove the last vestiges of the old 'from client' install method, in the form of 'if ($GL_PACKAGE_HOOKS)' lines - clean up the symlinking to be more precisely in line with doc/hook-propagation.mkd (especially, remove the 'quirk' that package hooks would also get copied to the user hooks area)
| * make log_it() put out a little more info if called prematurelySitaram Chamarty2012-02-211-1/+3
| |
| * simplified steps for moving serversSitaram Chamarty2012-02-211-65/+28
| | | | | | | | | | | | | | | | | | The instructions were written before gl-admin-push was created, I guess, making things sound a lot more complicated than they should be. Thanks to Nick (see gitolite mailing list messages, subject line "replicating a gitolite installation") for helping me realise this needed fixing.
| * gitolite.rc.mkd - documentation updateswu-lee2012-02-161-10/+19
| | | | | | | | | | | | | | - use single quotes in examples for GL_GITCONFIG_KEYS regex, and briefly explain why - emphasise that $GL_GITCONFIG_KEYS patterns match the whole key
| * replace <<EOF type constructs with multi-line echoSitaram Chamarty2012-02-143-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* | Add find_pubkey() functionChristian Ruppert2012-02-180-0/+0
| |
* | Add export_key_metadata() functionChristian Ruppert2012-02-181-0/+68
| |
* | Parse and export metadataChristian Ruppert2012-02-184-0/+44
| |
* | Improved setup_authkeys() functionChristian Ruppert2012-02-181-30/+44
| |
* | Allow one to specify a per repository umaskChristian Ruppert2012-02-173-3/+28
| |