| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
Not sure if this is needed to avoid it trying to run an editor. Probably
there is never a controlling terminal and probably git notices and does
nothing. But I'm just copying what I have in git-annex assistant here.
(Although with a much worse git version comparion, that only really works due
to luck.)
|
| |
|
|
| |
commits with an empty commit message.
|
| |
|
|
| |
All existing tests pass.
|
| |
|
|
|
|
| |
A file may have no git sha1 if it's in the underlay, or just is not checked
into git. This debug message doesn't add any value and is potentially
confusing.
|
| |
|
|
|
| |
ikiwiki source files can contain at least one character that
needs to be escaped in an url: +
|
| |
|
|
|
|
|
|
|
|
|
| |
When the wiki is in a subdir of the git repo, a web revert would show
in recentchanges as eg, doc/index, instead of just index.
This happened because decode_git_file caches a $prefix that is dependant
on the $git_dir setting, and the revert code runs with a different
$git_dir, which polluted the $prefix for later.
Fix this by adding a with_git_dir that juggles the variables properly.
|
| |
|
|
| |
When reverting, an add is a remove, and a remove is an add.
|
| |
|
|
| |
changes to attachments.
|
| | |
|
| |
|
|
| |
reading in enormous commits.
|
| |
|
|
| |
like recentchanges files that are not normally checked in, when fixing links after rename.
|
| | |
|
| |
|
|
| |
Signed-off-by: Tuomas Jormola <tj@solitudo.net>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
I understand the need to avoid chdir when running git_parse_changes
for receive now. At that point, the changes have not been pushed to
the srcdir's repo yet. When running the same code for preprevert,
chdir to the srcdir is ok, and necessary.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
errors from conflicting obsolete remote branches.
|
| |
|
|
|
| |
The wrapper is pointless in that configuration. Also, the code for it
doesn't compile w/o untrusted commiters to test. :)
|
| |
|
|
| |
jrayhawk)
|
| |
|
|
|
|
| |
Probably best to store it unsanitized and sanitize as needed on use.
And it already was for comments, leaving only the need to sanitize the
nickname when git committing, to ensure the email address is legal.
|
| |
|
|
| |
the git wrapper push to github in the background after ikiwiki runs.
|
| | |
|
| |
|
|
|
|
|
| |
Renamed usershort => nickname.
Note that this means existing user login sessions will not have the nickname
recorded, and so it won't be used for those.
|
| |
|
|
| |
display of ugly google openids.)
|
| |
|
|
|
|
|
|
|
|
| |
There was some confusion about whether the filename was
relative to srcdir or not. Some test cases, and the bzr
plugin assumed it was relative to the srcdir. Most everything else
assumed it was absolute.
Changed it to relative, for consistency with the rest
of the rcs_ functions.
|
| |
|
|
|
|
|
|
|
|
|
| |
Using named parameters for these is overdue. Passing the session in a
parameter instead of passing username and IP separately will later allow
storing other session info, like username or part of the email.
Note that these functions are not part of the exported API,
and the prototype change will catch (most) skew, so I am not changing
API versions. Any third-party plugins that call them will need updated
though.
|
| |
|
|
|
| |
that may contain the username component of the email address of
the user making the commit.
|
| |
|
|
|
|
|
|
|
|
| |
Now the git plugin supports commits with author fields that look like:
Author: http://my.openid/ <me@web>
Then in recentchanges, the short username will be displayed, linking
to the openid.
Particularly useful for the horrible google openids, of course.
|
| |
|
|
| |
run_or_die returns a status code in scalar context
|
| |
|
|
|
| |
In passing, fixed a bug where the srcdir was in a subdir of a repository
named "0".
|
| |
|
|
|
|
|
|
|
|
| |
* Automatically run --gettime the first time ikiwiki is run on
a given srcdir.
* Optimise --gettime for git, so it's appropriatly screamingly
fast. (This could be done for other backends too.)
* However, --gettime for git no longer follows renames.
* Use above to fix up timestamps on docwiki, as well as ensure that
timestamps on basewiki files shipped in the deb are sane.
|
| |
|
|
|
|
|
|
| |
* Rename --getctime to --gettime. (The old name still works for
backwards compatability.)
* --gettime now also looks up last modification time.
* Add rcs_getmtime to plugin API; currently only implemented
for git.
|
| |
|
|
| |
plugins from the setup file.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
Meh, git.
|