| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2010-04-05 | comments: Fix missing entity encoding in title. | Joey Hess | |
| The meta title data set by comments needs to be encoded the same way that meta encodes it. (NB The security implications of the missing encoding are small.) Note that meta's encoding of title, description, and guid data, and not other data, is probably a special case that should be removed. Instead, these values should be encoded when used. I have avoided doing so here because that would mean forcing a wiki rebuild on upgrade to have the data consitently encoded. | |||
| 2010-04-05 | response | Joey Hess | |
| 2010-04-05 | potential performance improvements | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-05 | speed | Joey Hess | |
| 2010-04-04 | fix test suite | Joey Hess | |
| 2010-04-04 | close bug, comment | Joey Hess | |
| 2010-04-04 | more idiomatic perl | Joey Hess | |
| 2010-04-04 | rename hash and avoid unnecessary hash ref | Joey Hess | |
| Variable renamed to be a bit more self-explanatory. Probably more idiomatic perl to not use a hash ref when a hash can be used. | |||
| 2010-04-04 | changelog | Joey Hess | |
| 2010-04-04 | fix indentation & whitespace | Joey Hess | |
| 2010-04-04 | Fix bzr plugin to work with bzr 2.0. | Lars Wirzenius | |
| The output of "bzr log" seems to have changed a bit, so we change the parsing accordingly. This has not been tested with earlier versions of bzr. Several problems seemed to occur, all in the bzr_log subroutine: 1. The @infos list would contain an empty hash, which would confuse the rest of the program. 2. This was because bzr_log would push an empty anonymous hash to the list whenever it thought a new record would start. 3. However, a new record marker (now?) also happens at th end of bzr log output. 4. Now we collect the record to a hash that gets pushed to the list only if it is not empty. 5. Also, sometimes bzr log outputs "revno: 1234 [merge]", so we catch only the revision number. 6. Finally, there may be non-headers at the of the output, so we ignore those. | |||
| 2010-04-04 | advertise some bugfixes | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-04 | bug report + patch: unnecessary YAML::Any dependency | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-04 | (no commit message) | http://hendry.iki.fi/ | |
| 2010-04-04 | Typo. | PaulePanter | |
| 2010-04-04 | (no commit message) | http://liw.fi/ | |
| 2010-04-04 | (no commit message) | http://liw.fi/ | |
| 2010-04-04 | (no commit message) | http://liw.fi/ | |
| 2010-04-04 | Add the Banu website | https://mukund.startssl.com/ | |
| 2010-04-04 | Remove my homepage | https://mukund.startssl.com/ | |
| 2010-04-04 | updated branch | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-04 | update fieldsort plugin to be compatible with the latest version of my branch | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-03 | answer about autofiles for tags | David Riebenbauer | |
| 2010-04-03 | link to commits | David Riebenbauer | |
| 2010-04-03 | slightly more consistent capitalisation of ikiwiki | Joey Hess | |
| For a while, I was avoiding capitalizing ikiwiki at the beginning of a sentence. I now think that's a bad idea (unless explicitly referring to the `ikiwiki` command). Still, I don't go all the way and always cap it, as a proper noun. That would make the logo look bad. ;) I also tend to avoid capping it as IkiWiki, except when referring to the perl internals, which do use that capitalization. (Too late to change that.) However, it's also reasonable to do so in a WikiLink, as a nod to historical camelcase wikis. | |||
| 2010-04-03 | add news item for ikiwiki 3.20100403 | Joey Hess | |
| 2010-04-03 | releasing version 3.20100403 | Joey Hess | |
| 2010-04-03 | fix buggy program installation code | Joey Hess | |
| 2010-04-03 | updated branch | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-02 | response | Joey Hess | |
| 2010-04-02 | response | Joey Hess | |
| 2010-04-03 | cross-reference | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-03 | vague musings about wikilinks | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-03 | perhaps the typedlink(tag foo) pagespec isn't so useful | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-03 | reduced difference | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-03 | sort-order could usefully be overridden for meta author, too | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-03 | actually I can see a second use for "nonlinear" syntax - but I don't think ↵ | http://smcv.pseudorandom.co.uk/ | |
| it's worth it | |||
| 2010-04-03 | make questions to Joey more explicit | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-03 | respond at some length | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-02 | respond (also unindent Joey's review to avoid very deep indentation) | http://smcv.pseudorandom.co.uk/ | |
| 2010-04-02 | idea | Joey Hess | |
| 2010-04-02 | comments | Joey Hess | |
| 2010-04-02 | minor comment | Joey Hess | |
| 2010-04-02 | fix branch name | Joey Hess | |
| 2010-04-02 | qualify template_file | Joey Hess | |
| 2010-04-02 | template: Search for templates in the templatedir, if they are not found as ↵ | Joey Hess | |
| pages in the wiki. | |||
| 2010-04-02 | review from the woods | Joey Hess | |
| 2010-04-02 | htmlscrubber: Allow colons in url fragments after '?' | Joey Hess | |
| Colons are not allowed at the start of urls, because it can be interpreted as a protocol, and allowing arbitrary protocols can be unsafe (CVE-2008-0809). However, this check was too restrictive, not allowing use of eg, "video.ogv?t=0:03:00/0:04:00" to seek to a given place in a video, or "somecgi?foo=bar:baz" to pass parameters with colons. It's still not allowed to have a filename with a colon in it (ie "foo:bar.png") -- to link to such a file, a fully qualified url must be used. | |||
| 2010-04-02 | Despam, again. Someone ban adrianna please? | Simon McVittie | |
| 2010-04-02 | (no commit message) | adrianna | |
 |
index : ikiwiki-upstream | |
| Unnamed repository; edit this file to name it for gitweb. | Jonas Smedegaard |
| summaryrefslogtreecommitdiff |