> Hi there,
> I've been using Subversion for a while now, and it's really nice. I
> especially like the option to have a human-friendly front-end through
> HTTP (with the cute XSL option, and all - I've written my own
> stylesheet). I was thinking about how this could be made to be a
> little more functional, though, in a way that would not be hard to
> implement (even though I don't have too much knowledge about
> Subversion source).
> So, I was thinking: it would be useful to have a ?rev= or ?revision=
> GET parameter. When using HTTP as the client protocol, there's
> probably some extra header that sets the revision to be retrieved, but
> for the web frontend, it would be nice to have a parameter that allows
> for easy viewing of an old version of a document (making viewcvs etc.
> a little less needed).
> For bonus points, all the href attributes could be rewritten (though
> this could be implemented in the XSL-sheet easily) to use the given
> revision. For extra bonus points, also allow for using keywords like
> HEAD and BASE in the parameter.
> So, would this be worth an issue in the issue tracker? Any thoughts?
The primary goal of mod_dav_svn is to be a gateway to the repository.
The secondary goal is to provide autoversioning for DAV client.
The very basic level of repository browsing is present only because it was
necessary to make plain GETs of files work for DAV, and extending that to
directories was only a quite small extra piece of code - but mod_dav_svn
does not really aim to be a repository browser.
In the interests of keeping the mod_dav_svn code concise and maintainable,
it seems better to me to use a dedicated repository browser rather than try
to make mod_dav_svn present two _very_ different perspectives. If ViewCVS is
not to your liking, there are *many* other possibilities - if you want a
pure Apache module solution, you could look into mod_svn_view.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Feb 5 22:23:10 2005