DON'T USE THIS! --- web frontend for git https://git.causal.agency/cgit-pink/atom?h=1.4.0 2022-05-15T17:10:57+00:00 2022-05-15T17:10:57+00:00 June McEnroe june@causal.agency 2022-05-15T17:10:57+00:00 urn:sha1:4a30da89c936102afc1666f106cc007ef5f2e1c0 2022-05-13T20:07:35+00:00 Hristo Venev hristo@venev.name 2022-05-07T17:07:00+00:00 urn:sha1:695515801c9241f106f6f99b04dc0e84439fdea5 sendfile() can return after a short read/write, so we may need to call it more than once. As suggested in the manual page, we fall back to read/write if sendfile fails with EINVAL or ENOSYS. On the read/write path, use write_in_full which deals with short writes. Signed-off-by: Hristo Venev <hristo@venev.name> 2022-05-13T19:42:03+00:00 Christian Hesse mail@eworm.de 2022-05-09T07:30:09+00:00 urn:sha1:069d15447b2ca1db8cd90959ae69bab0426959e2 Update to git version v2.36.1, no additional changes required. Signed-off-by: Christian Hesse <mail@eworm.de> 2022-05-13T19:42:03+00:00 Christian Hesse mail@eworm.de 2022-04-18T20:17:39+00:00 urn:sha1:3374b0e7a6a4a221e7778f6c8294beef987bcd27 Update to git version v2.36.0, this requires changes for these upstream commits: * 95433eeed9eac439eb21eb30105354b15e71302e diff: add ability to insert additional headers for paths Signed-off-by: Christian Hesse <mail@eworm.de> 2022-02-18T00:16:05+00:00 John Keeping john@keeping.me.uk 2022-02-13T15:34:50+00:00 urn:sha1:400fd7abbc9cf104999afeb05a7a40b8d58814b2 Instead of calling two separate Git functions to free memory associated with a commit object, use Git's wrapper which does this. This also counts as a potential future bug fix since release_commit_memory() also resets the parsed state of the commit, meaning any attempt to use it in the future will correctly fill out the fields again. release_commit_memory() does not set parents to zero, so keep that for additional safety in case CGit checks this without calling parse_commit() again. Signed-off-by: John Keeping <john@keeping.me.uk> 2022-02-18T00:11:05+00:00 John Keeping john@keeping.me.uk 2022-02-13T15:35:29+00:00 urn:sha1:93ce8fe3b1b3be2926c501145cce71ac86717202 In Firefox, the hashes in the blame UI are out of step with the line number and content leading to ever increasing vertical misalignment. This is caused by the .oid class setting font-size to 90%, so override this back to 100% for the blame case, bringing the height of lines in all three columns of the table back into step. Signed-off-by: John Keeping <john@keeping.me.uk> 2022-02-18T00:01:45+00:00 John Keeping john@keeping.me.uk 2022-02-13T15:29:06+00:00 urn:sha1:28c0cb6f72a8f2d0f5afcd854261aebdf832012b When walking through the history, it is useful to quickly see the same file at the previous revision, so add a link to do this. It would be nice to link to the correct line with an additional fragment, but this requires significantly more work so it can be done as an enhancement later. (ent->s_lno is mostly the right thing, but it is the line number in the post-image of the target commit whereas the link is to the parent of that commit, i.e. the pre-image of the target.) Suggested-by: Alejandro Colomar <alx.manpages@gmail.com> Signed-off-by: John Keeping <john@keeping.me.uk> 2022-02-18T00:00:57+00:00 lemon lsof@mailbox.org 2022-02-08T11:37:45+00:00 urn:sha1:c5809a4296f852fe30a7356854d3d0758fa1bf7f vsnprintf returns the byte count of the formatted output not including the null terminator, so in the case that len == 1024 the last character of the output was being truncated and not detected by the later check. Changing the greater than comparison to greater than or equal fixes this edge case. 2022-02-17T22:57:00+00:00 Christian Hesse mail@eworm.de 2022-01-10T09:18:55+00:00 urn:sha1:129d8a1582b586718a64bbbef393d529b84c7b16 Reading the README from repository used to be limited to default branch or a branch given in configuration. Let's allow a branch from query if not specified explicitly. 2022-02-14T02:13:41+00:00 June McEnroe june@causal.agency 2022-02-14T02:10:59+00:00 urn:sha1:44a004809b93dc1e6b174e41c2a5b4ac14f94d9b