Michael Jones schrieb: > On Sun, Feb 8, 2009 at 11:57 PM, Dan Craig <[email protected]> wrote: >> >> I'd be interested in that, too. I suppose it's quite dependent on the >> VCS you're using. > > I'd prefer it completely unrelated to the VCS. I'd rather it was a > diff based on versions that you publish, though I realise that might > coincide with your VCS checkins. I thought this would be possible as > the sources are distributed with the html output (not sure about other > output formats.) > >> My guess is that you'd want to write a script, >> whether incorporated into sphinx or not, that generates a rst file >> with the revision history info that gets incorporated into the >> document. Can you call functions in conf.py? >> > > Yeah, that's pretty much it. Though it could be an extension with a > directive to generate the change log and a config value to indicate > the path to the last published version. > > Just a thought really, wondering if anyone had implemented something > similar. I might take a crack at it in the distance future.
We had a discussion about a changelog some time ago. I think the conclusion was that, if you don't want to generate it from the VCS, you have to write it down somewhere anyway, and so why not just write it as a reST document you can include? I've done that with the Sphinx CHANGES file for example. Another part of the discussion was whether to have a directive that automatically generates an RSS feed from its contents (which would then at least have to be a list). This is still a valid feature request. Georg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~----------~----~----~----~------~----~------~--~---
