[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r1817718 - /subversion/site/staging/docs/index.html / Reinstate 1.6 API docu

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sun, 10 Dec 2017 16:54:15 +0000

Stefan wrote on Sun, 10 Dec 2017 17:00 +0100:
> Note that I'd reinstate the old 1.6 docus directly on publish (rather
> than on staging) since this would be easier to do (i.e. reverting the
> corresponding changes from r1696552 which obviously were done on publish).

Given that staging/ is a branch of publish/, it _should_ work to make
the revert on staging/ first. It would be good dogfooding, too. But as
always, he who does the legwork makes the calls.

> Any objections and/or better ideas?

I like the idea.

That said, a question. svnbook has a problem where search engines offer
the 1.x book (for some x<8) as the first result. Can we avoid this
problem happening for the doxygen docs?

IIRC there's an HTML tag that can be set to state "A newer version of
this doc is at <location/>", but I don't remember what it is, and I
realise it might not be straightforward to inject that tag into
generated docs.
Received on 2017-12-10 17:54:20 CET

This is an archived mail posted to the Subversion Dev mailing list.