A hyperfast web frontend for git repositories written in C. http://git.cetero.st/cgit/atom/ui-log.c?h=v1.0 2016-05-12T15:19:20Z 2016-05-12T15:19:20Z Tim Nordell tim.nordell@logicpd.com 2016-02-26T20:58:41Z urn:sha1:59d8fa1a62e7c19911fdf7ee9ceb0fdf8fa3331c The decoration code inside of git returns the decoration type, so utilize this to create the decoration spans. Additionally, use prettify_refname(...) to get the shorter name for the ref. Signed-off-by: Tim Nordell <tim.nordell@logicpd.com> 2016-05-12T15:17:02Z Tim Nordell tim.nordell@logicpd.com 2016-02-26T20:57:30Z urn:sha1:499b23979cd29513df16e4c2acce934932e09f7a The decoration span does not need to be emited if there aren't any decorations to show. This modification saves slightly on bandwidth. Signed-off-by: Tim Nordell <tim.nordell@logicpd.com> 2016-02-08T13:22:21Z John Keeping john@keeping.me.uk 2016-01-19T19:33:05Z urn:sha1:f2a901d2e1db5217d6890b26c6dc1ec119505d02 This affects the tooltip showing the full time and the case when a date is sufficiently old to be shown in full rather than as an offset. Signed-off-by: John Keeping <john@keeping.me.uk> 2016-02-08T13:19:33Z John Keeping john@keeping.me.uk 2016-01-19T19:33:01Z urn:sha1:57ea1aa2a5eab7f6aba702b3366fe4dcc72124f6 We never use any format other than FMT_SHORTDATE, so move that into the function. Signed-off-by: John Keeping <john@keeping.me.uk> 2016-01-17T16:05:00Z John Keeping john@keeping.me.uk 2016-01-16T11:03:05Z urn:sha1:baa5ad1f80f56d3c0b0095bfb468fab28c9b4982 If parse_commit() fails, none of the fields in the commit structure will have been populated so we will dereference NULL when accessing item->tree. There isn't much we can do about the error at this point, but if we return true then we'll try parsing the commit again from print_commit() and we can report an error to the user at that point. Coverity-id: 13801 Signed-off-by: John Keeping <john@keeping.me.uk> 2016-01-13T16:12:17Z Christian Hesse mail@eworm.de 2016-01-05T06:38:53Z urn:sha1:559ab5ecc4445c8477ecf62c9fc97efa412dd562 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 <mail@eworm.de> 2015-08-14T13:46:51Z John Keeping john@keeping.me.uk 2015-08-14T11:47:15Z urn:sha1:23c17d8ff01b96619bc1f71274cb44f1425e10f4 Signed-off-by: John Keeping <john@keeping.me.uk> 2015-08-12T15:43:08Z John Keeping john@keeping.me.uk 2015-08-12T15:41:34Z urn:sha1:da1d4c77760ff6a0eb5cbfbaf6956930089d1963 This crept in while rebasing the previous commit onto an updated upstream. Signed-off-by: John Keeping <john@keeping.me.uk> 2015-08-12T14:57:46Z John Keeping john@keeping.me.uk 2015-08-12T14:55:28Z urn:sha1:30304d8156a72ffc95e45e1aa9407319b81bd253 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 <necoro@necoro.eu> Signed-off-by: John Keeping <john@keeping.me.uk> 2015-08-12T12:09:05Z Christian Hesse mail@eworm.de 2015-07-28T08:42:01Z urn:sha1:de83de276bef7509ab8255682595ad4521f3a193 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 <mail@eworm.de>