aboutsummaryrefslogtreecommitdiff
path: root/IkiWiki/Plugin/git.pm
Commit message (Expand)AuthorAge
* Group related plugins into sections in the setup file, and drop unused rcs pl...Joey Hess2010-02-11
* handle git-notes breakage•••The new git-notes feature in git 1.6.6 changes git log output in a way that broke ikiwiki's parser if notes are added to commits. I decided to deal with this by disabling notes when ikiwiki uses git, by setting GIT_NOTES_REF="". AFAICS, looking up notes when dumping logs will only waste time, since it does not currently seem to make sense for ikiwiki to do anything with the notes. Joey Hess2010-01-19
* brace style and layoutJoey Hess2010-01-18
* skip merges•••git log --follow seems to sometimes show merges from before the file was ever created. So, skip them, a file shouldn't be first created during a merge anyway. Joey Hess2009-10-12
* can't use --reverse with git log --follow•••Meh, git. Joey Hess2009-10-11
* git: --getctime will now follow renames back to the original creation of a file.•••This will be a bit more expensive, but --getctime does not need to be fast. And getting the real creation time a very useful when untangling blog histories that involve renames. Joey Hess2009-10-11
* clean up use of IkiWiki::Receive•••Loading and use of IkiWiki::Receive can all be pushed into the git plugin, rather than scattered around. I had at first wanted to make a receive plugin and move it there, but a plugin was not a good fit; you don't want users to have to manually load it, and making the git plugin load the receive plugin at the right times would need more, and ugly code. Joey Hess2009-09-10
* fix rcs_getctime to return first, not last, change time•••This was being buggy and returning the file's last change time, not its creation time. (I checked all the others (except tla) and they're ok.) Joey Hess2009-03-20
* git: Manually decode git output from utf-8, avoids warning messages on invali...Joey Hess2009-03-09
* git: Fix utf-8 encoding of author names.•••I guess what's happening here is that since the name is passed to git via an environment variable, perl's normal utf-8 IO layer stuff doesn't work. So we have to explicitly decode the string from perl's internal representation into utf-8. Joey Hess2009-03-09
* git: Fix malformed utf8 recieved from git.•••If git log outputs malformed utf8 in, eg, usernames, detect it and fix it up. This avoids commits such as f71abc92aa279fbe0b7578b8c4752d775dd4a259 breaking things. Joey Hess2009-01-25
* A recent change to gitweb removed support for the form of diffurl that many ...Joey Hess2009-01-05
* 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 all•••It needs to write to the user db. Joey Hess2008-10-24
* include temp file for attachment change tooJoey Hess2008-10-24
* updatesJoey Hess2008-10-24
* untrusted committers code seems to be fully working•••Still need to investigate possible races, and test some more. Joey Hess2008-10-23
* check_canattach hooked upJoey Hess2008-10-23
* more work on untrusted committers•••Wired up check_canedit and check_canremove, still need to deal with check_canattach, and test. Joey Hess2008-10-23
* initial support for git repos with untrusted committers•••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. Joey Hess2008-10-22
* git: Fix handling of utf-8 filenames in recentchanges.•••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? Joey Hess2008-09-25
* change git hook description•••It doesn't have to be a post-update hook. Joey Hess2008-09-11
* add plugin safe/rebuild info (part 1 of 2)•••too many plugins.. brain exploding.. Joey Hess2008-08-03
* show unsafe options (RO) by default•••Small data leak, but only to admins, and I think it's worth it to see the stuff that cannot be configured. Joey Hess2008-08-02
* rcs plugin loading reorg•••Move rcs plugin load to loadplugins; move duplicate rcs detection logic out of individual plugins and into loadplugins. Avoids checkconfig failing when run twice. Joey Hess2008-08-01
* Merge branch 'master' into autoconfig•••Conflicts: IkiWiki/Plugin/git.pm debian/changelog po/ikiwiki.pot Joey Hess2008-07-31
* 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