DON'T USE THIS! --- web frontend for git https://git.causal.agency/cgit-pink/atom?h=1.3.0 2022-02-14T02:13:41+00:00 2022-02-14T02:13:41+00:00 June McEnroe june@causal.agency 2022-02-14T02:10:59+00:00 urn:sha1:44a004809b93dc1e6b174e41c2a5b4ac14f94d9b 2022-02-14T02:10:50+00:00 June McEnroe june@causal.agency 2022-02-14T01:20:07+00:00 urn:sha1:76d9396e47ce00b029ba4497fd63aa507929fcd3 2022-02-13T23:24:04+00:00 June McEnroe june@causal.agency 2021-01-20T18:33:37+00:00 urn:sha1:d993e4be6731b1a806e2c7588334a3f485a5fd31 Lua support is unused and the dlsym fwrite/write hacks horrify me. Clean it up. 2022-02-13T17:24:41+00:00 June McEnroe june@causal.agency 2022-02-13T17:22:42+00:00 urn:sha1:e4ce4fa747c246e1cfbad86c3e2b8e454146d211 2022-02-13T17:20:09+00:00 June McEnroe june@causal.agency 2021-09-30T19:49:37+00:00 urn:sha1:065ee253aef368e99899cde3839c2e801a95fb27 cgit runs in a chroot. It is normal that it cannot look up user info in /etc/passwd. 2022-02-13T17:18:51+00:00 June McEnroe june@causal.agency 2021-09-22T15:40:24+00:00 urn:sha1:f92ba7ea854f826816cdbf94bc2afa4104669961 I do not like these things. 2022-02-13T17:14:06+00:00 June McEnroe june@causal.agency 2021-09-06T17:31:04+00:00 urn:sha1:03519c7bc48bb58dc0c129f9e45c0e784f775bbb 2022-02-13T17:13:58+00:00 June McEnroe june@causal.agency 2021-06-08T20:21:10+00:00 urn:sha1:20f0352d9be4d6159ef665140d27ed8de76c0c91 Fixes several RFC 4287 violations: > 4.1.1. The "atom:feed" Element > o atom:feed elements MUST contain exactly one atom:id element. > o atom:feed elements SHOULD contain one atom:link element with a rel > attribute value of "self". This is the preferred URI for > retrieving Atom Feed Documents representing this Atom feed. > o atom:feed elements MUST contain exactly one atom:updated element. An atom:id element is generated from cgit_currentfullurl(), and an atom:link element with a rel attribute of "self" is generated with the same URL. An atom:updated element is generated from the date of the first commit in the revision walk. > 4.1.2. The "atom:entry" Element > o atom:entry elements MUST NOT contain more than one atom:content > element. The second atom:content element with the type of "xhtml" is removed. > 4.2.6. The "atom:id" Element > Its content MUST be an IRI, as defined by [RFC3987]. Note that the > definition of "IRI" excludes relative references. Though the IRI > might use a dereferencable scheme, Atom Processors MUST NOT assume it > can be dereferenced. The atom:id elements for commits now use URNs in the "sha1" or "sha256" namespaces. Although these are not registered URN namespaces, they see use in the wild, for instance as part of magnet URIs. 2022-02-13T17:10:49+00:00 June McEnroe june@causal.agency 2022-02-13T17:07:49+00:00 urn:sha1:516175469a8c6895496ef909b487992deb45f460 2022-02-13T16:57:33+00:00 June McEnroe june@causal.agency 2021-04-12T21:18:42+00:00 urn:sha1:12d91b897df65a2a50878edc62541c5b7f90003a For example any URL that starts with a real repo name but isn't valid.