| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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.)
|
| |
|
|
| |
invalidly encoded output.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
If git log outputs malformed utf8 in, eg, usernames, detect it and fix it
up. This avoids commits such as f71abc92aa279fbe0b7578b8c4752d775dd4a259
breaking things.
|
| |
|
|
| |
ikiwiki setups use. Document how to use the new url form.
|
| | |
|
| | |
|
| |
|
|
| |
It needs to write to the user db.
|
| | |
|
| | |
|
| |
|
|
| |
Still need to investigate possible races, and test some more.
|
| | |
|
| |
|
|
|
| |
Wired up check_canedit and check_canremove, still need to deal with
check_canattach, and test.
|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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?
|
| |
|
|
| |
It doesn't have to be a post-update hook.
|
| |
|
|
| |
too many plugins.. brain exploding..
|
| |
|
|
|
| |
Small data leak, but only to admins, and I think it's worth it to see the
stuff that cannot be configured.
|
| |
|
|
|
|
| |
Move rcs plugin load to loadplugins; move duplicate rcs detection logic out
of individual plugins and into loadplugins. Avoids checkconfig failing when
run twice.
|
| |
|
|
|
|
|
|
| |
Conflicts:
IkiWiki/Plugin/git.pm
debian/changelog
po/ikiwiki.pot
|
| | |
|
| | |
|
| | |
|
| |
|