public inbox for [email protected]  

help / color / mirror / Atom feed

From: Marti Raudsepp <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: pgsql-www <[email protected]>
Cc: Stefan Kaltenbrunner <[email protected]>
Subject: Re: [PATCH] Cross-version navigation in documentation
Date: Wed, 30 May 2012 12:58:26 +0300
Message-ID: <CABRT9RBbNU17um=DW3VRLE0DW0ahanAo07bNLXsF73F+rhZgQA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CABRT9RCFpt35TdrrN0jsY3YfqMiiJOTTWYWpSQKYaEdcQZKugw@mail.gmail.com>
	<CABUevEyuu2kJhqjv9kSovuwg99sKf5zYKASXf=3d8ffKnQZ4aA@mail.gmail.com>
	<[email protected]>

On Mon, May 28, 2012 at 2:44 PM, Andres Freund <[email protected]> wrote:
> The amount of pages actually having been renamed isn't that big. Marti opened
> up his version of the docs to me and I browsed along and even between 7.4 and
> 9.1 I had a hard time finding pages where you would expect a link from 7.4
> forwards.

Exactly. And people rely on page names right now anyway -- they find
the page on Google and then just change the version number in the URL
and see if it works. Either that, or they will read the wrong version.
What I'm proposing solves >95% of the cases and I think that is good
enough.

In theory we could mine git history to extract page
renames/merges/splits, but it sounds like a lot of effort for little
gain.

On Sun, May 27, 2012 at 9:40 PM, Magnus Hagander <[email protected]> wrote:
> On Sunday, May 27, 2012, Marti Raudsepp wrote:
>> PS: Python projects have a nearly universal style of using 4-space
>> indents (PEP-0008).

> I don't really see the point. If your editor can't be consistent about
> tabs/spaces, you probably have a bigger problem

Well I need to reconfigure my editor to edit these files.

>> 0001-Allow-documentation-loading-without-tidy-Tidylib-for.patch
> More to the point though - if we want a feature like that, it should be
> controlled by a parameter that turns it off, not by automatically doing it.

Ok, agreed.

Regards,
Marti

view thread (14+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [PATCH] Cross-version navigation in documentation
  In-Reply-To: <CABRT9RBbNU17um=DW3VRLE0DW0ahanAo07bNLXsF73F+rhZgQA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox