i wrote:
|"Upstream" git is now served by
|
| {http,https}://git.sdaoden.eu/cgit{,/s-nail.git}.
This is still true, but you'd save yourself a redirect when you
change this to git.sdaoden.eu/scm/*, which is henceforth available
and backed directly by the smarter git-http-backend.
I have also recognized that some people desparately tried to look
at some commits on the [heirloom] branch, which then sometimes
seems to have ended in a kind of "invalid branch" message, whereas
switching to "diff" mode works, switching back to "commit" fails
again (yes i've tried to repeat _that_ mysterious usage pattern).
For the above change i've completely reconfigured the git/cgit
approach, now with world-readable repositories and directly run
CGI programs (instead of going through some UID-changer first).
All files were group-readable already, however, and thus this may
indeed be a cgit bug in the end.
..while writing, on [next] i've changed the new `colour' stuff to
its final approach, it now takes the mode to work on ("colour 256
STUFF", "colour iso STUFF" etc.) and is configured through
termcap/terminfo, to be overwritten by the new *termcap* (even
without WANT_TERMCAP), as in -Stermcap=Co=256. I.e., that
terrible *colour-terms* hack is gone, we now configure ourselfs
automatically to the right value.
Ciao!
--steffen
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
__________________________________
[email protected]
