public inbox for [email protected]  

help / color / mirror / Atom feed

From: David G. Johnston <[email protected]>
To: Jürgen Purtz <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Additional Chapter for Tutorial
Date: Mon, 26 Oct 2020 07:53:43 -0700
Message-ID: <CAKFQuwbtReW3dBO0HmZCb8rF4z-w+oFt24nPko8pbAk4Y2VWEw@mail.gmail.com> (raw)
In-Reply-To: <CAKFQuwbqiZ4Er_e21oXt8J_JDyNucLMcW7murkMr0v=pTy10RA@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAKFQuwZ_USvnhZ5wQLFtpr8v+iMiwvZOiVZhviQwPYGDVR7w+g@mail.gmail.com>
	<[email protected]>
	<CAKFQuwbqiZ4Er_e21oXt8J_JDyNucLMcW7murkMr0v=pTy10RA@mail.gmail.com>

Removing -docs as moderation won’t let me cross-post.

On Monday, October 26, 2020, David G. Johnston <[email protected]>
wrote:

> On Monday, October 26, 2020, Jürgen Purtz <[email protected]> wrote:
>
>> On 21.10.20 22:33, David G. Johnston wrote:
>>
>>
>> Two, I find the amount of detail being provided here to be on the
>> too-much side.  A bit more judicious use of links into the appropriate
>> detail chapters seems warranted.
>>
>> The patch is intended to give every interested person an overall
>> impression of the chapter within its new position. Because it has moved
>> from part 'Tutorial' to 'Internals' the text should be very accurate
>> concerning technical issues - like all the other chapters in this part. A
>> tutorial chapter has a more superficial nature.
>>
> Haven’t reviewed the patches yet but...
>
> I still think that my comment applies even with the move to internals.
> The value here is putting together a coherent narrative and making deeper
> implementation details accessible.  If those details are already covered
> elsewhere in the documentation (not source code) links should be given
> serious consideration.
>
> David J.
>
>

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]
  Subject: Re: Additional Chapter for Tutorial
  In-Reply-To: <CAKFQuwbtReW3dBO0HmZCb8rF4z-w+oFt24nPko8pbAk4Y2VWEw@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