On 02/13/2014 01:25 AM, Tom Lane wrote:
> Committed. Thanks for doing what sure looks like a mind-numbingly
> tedious bit of editing.
Thank you for committing it!
--
Vik
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresq
Vik Fearing writes:
> On 01/20/2014 08:35 AM, Tom Lane wrote:
>> Why didn't you follow the existing style for the major-version links?
>> That is, a pattern like
>> However, if you are upgrading from a version earlier than 9.0.6,
>> see .
> I believe to have addressed your concerns in this new pa
On 02/12/2014 03:40 PM, Tom Lane wrote:
Peter Eisentraut writes:
I think it would be even better to link directly to the migration notes,
not to the top-level section of the release notes. I suggest to add a
link target like
Migration to Version 9.2.4
and then link to that.
I
Peter Eisentraut writes:
> I think it would be even better to link directly to the migration notes,
> not to the top-level section of the release notes. I suggest to add a
> link target like
>
>Migration to Version 9.2.4
> and then link to that.
I experimented with this and didn't reall
On Mon, 2014-01-20 at 16:42 +0100, Vik Fearing wrote:
> I believe to have addressed your concerns in this new patch. I did
> not
> do "make postgres.txt" on the previous version, but I did do it on
> this
> one and it looks okay to me.
I think it would be even better to link directly to the migra
On 01/20/2014 04:42 PM, Vik Fearing wrote:
> On 01/20/2014 08:35 AM, Tom Lane wrote:
>> Vik Fearing writes:
>>> The attached patch aims to help upgraders find the relevant information
>>> important to their upgrade.
>> This seems like a good idea, but bad implementation.
>>
>> [...]
> I believe to
Vik Fearing writes:
> The attached patch aims to help upgraders find the relevant information
> important to their upgrade.
This seems like a good idea, but bad implementation.
Why didn't you follow the existing style for the major-version links?
That is, a pattern like
However, if you are
