aboutsummaryrefslogtreecommitdiff
path: root/IkiWiki/Plugin/git.pm
Commit message (Collapse)AuthorAge
* Coding style change: Remove explcit vim folding markers.Joey Hess2008-12-17
|
* git: Allow [[sha1_commit]] to be used in the diffurl, to support cgit.Joey Hess2008-10-27
|
* the pre-receive wrapper needs to be suid after allJoey Hess2008-10-24
| | | | It needs to write to the user db.
* include temp file for attachment change tooJoey Hess2008-10-24
|
* updatesJoey Hess2008-10-24
|
* untrusted committers code seems to be fully workingJoey Hess2008-10-23
| | | | Still need to investigate possible races, and test some more.
* check_canattach hooked upJoey Hess2008-10-23
|
* more work on untrusted committersJoey Hess2008-10-23
| | | | | Wired up check_canedit and check_canremove, still need to deal with check_canattach, and test.
* initial support for git repos with untrusted committersJoey Hess2008-10-22
| | | | | Still need to wire up the calls to check_* , but it's cold out here and my hands are going numb, so enough for now.
* git: Fix handling of utf-8 filenames in recentchanges.Joey Hess2008-09-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Seems that the problem is that once the \nnn coming from git is converted to a single character, decode_utf8 decides that this is a standalone character, and not part of a multibyte utf-8 sequence, and so does nothing. I tried playing with the utf-8 flag, but that didn't work. Instead, use decode("utf8"), which doesn't have the same qualms, and successfully decodes the octets into a utf-8 character. Rant: Think for a minute about fact that any and every program that parses git-log, or git-show, etc output to figure out what files were in a commit needs to contain this snippet of code, to convert from git-log's wacky output to a regular character set: if ($file =~ m/^"(.*)"$/) { ($file=$1) =~ s/\\([0-7]{1,3})/chr(oct($1))/eg; } (And it's only that "simple" if you don't care about filenames with embedded \n or \t or other control characters.) Does that strike anyone else as putting the parsing and conversion in the wrong place (ie, in gitweb, ikiwiki, etc, etc)? Doesn't anyone who actually uses git with utf-8 filenames get a bit pissed off at seeing \xxx\xxx instead of the utf-8 in git-commit and other output?
* change git hook descriptionJoey Hess2008-09-11
| | | | It doesn't have to be a post-update hook.
* add plugin safe/rebuild info (part 1 of 2)Joey Hess2008-08-03
| | | | too many plugins.. brain exploding..
* show unsafe options (RO) by defaultJoey Hess2008-08-02
| | | | | Small data leak, but only to admins, and I think it's worth it to see the stuff that cannot be configured.
* rcs plugin loading reorgJoey Hess2008-08-01
| | | | | | Move rcs plugin load to loadplugins; move duplicate rcs detection logic out of individual plugins and into loadplugins. Avoids checkconfig failing when run twice.
* Merge branch 'master' into autoconfigJoey Hess2008-07-31
| | | | | | | | Conflicts: IkiWiki/Plugin/git.pm debian/changelog po/ikiwiki.pot
* add guard against enabling multiple rcs pluginsJoey Hess2008-07-30
|
* avoid clobbering example diffurlJoey Hess2008-07-27
|
* finish with rcs plugin conversionJoey Hess2008-07-26
|
* Version control backends promoted to first-class pluginsJoey Hess2008-07-26