On Mon, Aug 13, 2012 at 12:26:36PM +0200, Michal Suchanek wrote: > On 11 August 2012 01:33, Chad Perrin <c...@apotheon.net> wrote: > > On Fri, Aug 10, 2012 at 10:13:06PM +0200, li...@martijn.coppoolse.com wrote: > >> > >> ...but of course, that doesn't contain a link to the download(s). > >> OTOH, why do you need to keep a link to this specific version, once > >> it gets older? > > > > Publishing an article about the current release version, for instance, > > would ideally be able to point to something about the specific release > > version, because otherwise in a year's time the article might be called > > something like "Fossil SCM 1.23 Provides New Features" with a link to > > release notes for Fossil SCM 2.1 or something like that. > > The page http://www.fossil-scm.org/download.html includes all the versions. > > I guess adding anchors so that a link to the part about a particular > release can be crafted would suffice.
That'd be nice. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
