A hyperfast web frontend for git repositories written in C. http://git.cetero.st/cgit/atom/ui-refs.c?h=v1.2.2 2019-06-05T13:37:49Z 2019-06-05T13:37:49Z Christian Hesse mail@eworm.de 2019-01-02T16:25:01Z urn:sha1:ccba7eb9d0c43ffe99178ab6632dc3794f887309 Signed-off-by: Christian Hesse <mail@eworm.de> 2018-06-27T16:11:19Z John Keeping john@keeping.me.uk 2018-03-31T14:11:05Z urn:sha1:71d14d9c98c39a6683780060f84429a3a7e5b348 cgit_compose_snapshot_prefix() is identical to print_tag_downloads(), so remove the latter and use the function from ui-shared.c instead. Signed-off-by: John Keeping <john@keeping.me.uk> Reviewed-by: Christian Hesse <mail@eworm.de> 2018-06-27T16:11:19Z John Keeping john@keeping.me.uk 2018-03-31T13:57:22Z urn:sha1:f0047d2d943788fed2666e1d20c1e0d3c16701d5 There is no way for refinfo::refname to be null, and Git will prevent zero-length refs so this check is unnecessary. Signed-off-by: John Keeping <john@keeping.me.uk> Reviewed-by: Christian Hesse <mail@eworm.de> 2018-06-27T16:11:19Z John Keeping john@keeping.me.uk 2018-03-31T13:20:01Z urn:sha1:c1572bb5ec4540b5008490cf471cc4a5e65ef728 Allow using a user-specified value for the prefix in snapshot files instead of the repository basename. For example, files downloaded from the linux-stable.git repository should be named linux-$VERSION and not linux-stable-$VERSION, which can be achieved by setting: repo.snapshot-prefix=linux Signed-off-by: John Keeping <john@keeping.me.uk> Reviewed-by: Christian Hesse <mail@eworm.de> 2016-07-05T14:14:40Z Lukas Fleischer lfleischer@lfos.de 2016-05-24T16:15:18Z urn:sha1:9984e7ab49c59e49a0d7e62c3435e7133f7a53ec When composing snapshot file names for a tag with a prefix of the form v[0-9] (resp. V[0-9]), the leading "v" (resp. "V") is stripped. This leads to conflicts if a tag with the stripped name already exists or if there are tags only differing in the capitalization of the leading "v". Make sure we do not strip the "v" in these cases. Reported-by: Juuso Lapinlampi <wub@partyvan.eu> Signed-off-by: Lukas Fleischer <lfleischer@lfos.de> 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> 2015-10-09T08:54:48Z John Keeping john@keeping.me.uk 2015-10-08T22:23:59Z urn:sha1:198a4404b937033cf2cf2b054242df4e81ef3075 There is no way that "tag" can be null here. Coverity-id: 13950 Signed-off-by: John Keeping <john@keeping.me.uk> 2015-08-14T13:46:51Z John Keeping john@keeping.me.uk 2015-08-14T11:47:16Z urn:sha1:6d39dd1914dd0a904c606b079e8ef0f1643f2266 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>