summaryrefslogtreecommitdiff
path: root/IkiWiki/Plugin/git.pm
AgeCommit message (Collapse)Author
2010-02-11Group related plugins into sections in the setup file, and drop unused rcs ↵Joey Hess
plugins from the setup file.
2010-01-19handle git-notes breakageJoey Hess
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.
2010-01-18brace style and layoutJoey Hess
2009-10-12skip mergesJoey Hess
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.
2009-10-11can't use --reverse with git log --followJoey Hess
Meh, git.
2009-10-11git: --getctime will now follow renames back to the original creation of a file.Joey Hess
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.
2009-09-10clean up use of IkiWiki::ReceiveJoey Hess
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.
2009-03-20fix rcs_getctime to return first, not last, change timeJoey Hess
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.)
2009-03-09git: Manually decode git output from utf-8, avoids warning messages on ↵Joey Hess
invalidly encoded output.
2009-03-09git: Fix utf-8 encoding of author names.Joey Hess
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.
2009-01-25git: Fix malformed utf8 recieved from git.Joey Hess
If git log outputs malformed utf8 in, eg, usernames, detect it and fix it up. This avoids commits such as f71abc92aa279fbe0b7578b8c4752d775dd4a259 breaking things.
2009-01-05A recent change to gitweb removed support for the form of diffurl that many ↵Joey Hess
ikiwiki setups use. Document how to use the new url form.
2008-12-17Coding style change: Remove explcit vim folding markers.Joey Hess
2008-10-27git: Allow [[sha1_commit]] to be used in the diffurl, to support cgit.Joey Hess
2008-10-24the pre-receive wrapper needs to be suid after allJoey Hess
It needs to write to the user db.
2008-10-24include temp file for attachment change tooJoey Hess
2008-10-24updatesJoey Hess
2008-10-23untrusted committers code seems to be fully workingJoey Hess
Still need to investigate possible races, and test some more.
2008-10-23check_canattach hooked upJoey Hess
2008-10-23more work on untrusted committersJoey Hess
Wired up check_canedit and check_canremove, still need to deal with check_canattach, and test.
2008-10-22initial support for git repos with untrusted committersJoey Hess
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.
2008-09-25git: Fix handling of utf-8 filenames in recentchanges.Joey Hess
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?
2008-09-11change git hook descriptionJoey Hess
It doesn't have to be a post-update hook.
2008-08-03add plugin safe/rebuild info (part 1 of 2)Joey Hess
too many plugins.. brain exploding..
2008-08-02show unsafe options (RO) by defaultJoey Hess
Small data leak, but only to admins, and I think it's worth it to see the stuff that cannot be configured.
2008-08-01rcs plugin loading reorgJoey Hess
Move rcs plugin load to loadplugins; move duplicate rcs detection logic out of individual plugins and into loadplugins. Avoids checkconfig failing when run twice.
2008-07-31Merge branch 'master' into autoconfigJoey Hess
Conflicts: IkiWiki/Plugin/git.pm debian/changelog po/ikiwiki.pot
2008-07-30add guard against enabling multiple rcs pluginsJoey Hess
2008-07-27avoid clobbering example diffurlJoey Hess
2008-07-26finish with rcs plugin conversionJoey Hess
2008-07-26Version control backends promoted to first-class pluginsJoey Hess