cgit/ui-log.c, branch v0.12

git: update to v2.7.0

2016-01-13T16:12:17Z

Update to git version v2.7.0. * Upstream commit ed1c9977cb1b63e4270ad8bdf967a2d02580aa08 (Remove get_object_hash.) changed API: Convert all instances of get_object_hash to use an appropriate reference to the hash member of the oid member of struct object. This provides no functional change, as it is essentially a macro substitution. Signed-off-by: Christian Hesse

log: move layout into page function

2015-08-14T13:46:51Z

Signed-off-by: John Keeping

ui-log: fix double counting

2015-08-12T15:43:08Z

This crept in while rebasing the previous commit onto an updated upstream. Signed-off-by: John Keeping

log: allow users to follow a file

2015-08-12T14:57:46Z

Teach the "log" UI to behave in the same way as "git log --follow", when given a suitable instruction by the user. The default behaviour remains to show the log without following renames, but the follow behaviour can be activated by following a link in the page header. Follow is not the default because outputting merges in follow mode is tricky ("git log --follow" will not show merges). We also disable the graph in follow mode because the commit graph is not simplified so we end up with frequent gaps in the graph and many lines that do not connect with any commits we're actually showing. We also teach the "diff" and "commit" UIs to respect the follow flag on URLs, causing the single-file version of these UIs to detect renames. This feature is needed only for commits that rename the path we're interested in. For commits before the file has been renamed (i.e. that appear later in the log list) we change the file path in the links from the log to point to the old name; this means that links to commits always limit by the path known to that commit. If we didn't do this we would need to walk down the log diff'ing every commit whenever we want to show a commit. The drawback is that the "Log" link in the top bar of such a page links to the log limited by the old name, so it will only show pre-rename commits. I consider this a reasonable trade-off since the "Back" button still works and the log matches the path displayed in the top bar. Since following renames requires running diff on every commit we consider, I've added a knob to the configuration file to globally enable/disable this feature. Note that we may consider a large number of commits the revision walking machinery no longer performs any path limitation so we have to examine every commit until we find a page full of commits that affect the target path or something related to it. Suggested-by: René Neumann Signed-off-by: John Keeping

git: update to v2.5.0

2015-08-12T12:09:05Z

Update to git version v2.5.0. * Upstream commit 5455ee0573a22bb793a7083d593ae1ace909cd4c (Merge branch 'bc/object-id') changed API: for_each_ref() callback functions were taught to name the objects not with "unsigned char sha1[20]" but with "struct object_id". * Upstream commit dcf692625ac569fefbe52269061230f4fde10e47 (path.c: make get_pathname() call sites return const char *) Signed-off-by: Christian Hesse

ui-log: make some variables 'static'

2015-03-09T16:39:20Z

These are not used outside this file and are not declared. Signed-off-by: John Keeping

tag: reference with "h" instead of "id"

2015-01-19T16:52:10Z

When clicking on "log" from a tag we end up showing the log of whatever branch we used to reach the tag. If the tag doesn't point onto a branch then the tagged commit won't appear in this output. By linking to tags with the head parameter instead of the "id" parameter the log link will show the log of the tag. This is clearly desirable when the tag has been reached from the refs UI and changing the behaviour for tag decorations makes them match branch decorations where log -> decoration -> log shows the log of the decoration. Reported-by: Ferry Huberts Signed-off-by: John Keeping

git: update to v2.2.1

2014-12-24T01:53:03Z

Update to git version v2.2.1, including API changes. Signed-off-by: Christian Hesse

ui-shared: remove toggle_ssdiff arg to cgit_commit_link()

2014-12-13T11:38:42Z

This argument is never used with a value other than zero, so remove it and simplify the code. Signed-off-by: John Keeping

git: update to v2.0.3

2014-07-28T00:01:35Z

This is slightly more involved than just bumping the version number because it pulls in a change to convert the commit buffer to a slab, removing the "buffer" field from "struct commit". All sites that access "commit->buffer" have been changed to use the new functions provided for this purpose. Signed-off-by: John Keeping