Minor Typo in SELECT docs
There is a reference to the "sql_interitance" configuration in the
7.4.x docs:
http://www.postgresql.org/docs/7.4/static/sql-select.html
I don't know whether their will be anything beyond 7.4.5, but this
would be an easy patch.
-tfo
Thomas F.O'Connell wrote:
There is a reference to the "sql_interitance" configuration in the 7.4.x
docs:
Since it's fixed in HEAD, I think we're fine -- we usually don't bother
applying documentation fixes to release branches, even if there were
plans for another 7.4.x release.
-Neil
On Fri, Sep 10, 2004 at 09:31:09AM +1000, Neil Conway wrote:
Thomas F.O'Connell wrote:
There is a reference to the "sql_interitance" configuration in the 7.4.x
docs:Since it's fixed in HEAD, I think we're fine -- we usually don't bother
applying documentation fixes to release branches, even if there were
plans for another 7.4.x release.
Oh, is this really a good policy?
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"I personally became interested in Linux while I was dating an English major
who wouldn't know an operating system if it walked up and bit him."
(Val Henson)
I second Alvaro: Why is that?
-tfo
On Sep 9, 2004, at 6:47 PM, Alvaro Herrera wrote:
Show quoted text
On Fri, Sep 10, 2004 at 09:31:09AM +1000, Neil Conway wrote:
Thomas F.O'Connell wrote:
There is a reference to the "sql_interitance" configuration in the
7.4.x
docs:Since it's fixed in HEAD, I think we're fine -- we usually don't
bother
applying documentation fixes to release branches, even if there were
plans for another 7.4.x release.Oh, is this really a good policy?
Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
On Fri, Sep 10, 2004 at 09:31:09AM +1000, Neil Conway wrote:
Since it's fixed in HEAD, I think we're fine -- we usually don't bother
applying documentation fixes to release branches, even if there were
plans for another 7.4.x release.
Oh, is this really a good policy?
It's not so much that we have a "policy" as that we have a finite number
of committers with finite time. If any committer wants to go and fix
this trivial typo in a back branch, no one will say boo. But I doubt
any of us will take the time either. There are a lot of typos besides
this one, and always have been. Personally I'd rather spend the time
proofing current docs.
regards, tom lane
Tom Lane wrote:
There are a lot of typos besides this one, and always have been.
Personally I'd rather spend the time proofing current docs.
Also, there's been a tendency in the past to not regenerate the online
docs for each point release in a stable branch (particularly for formats
like PS and PDF). So that's been another reason we haven't bothered with
this in the past. I tend to agree with Tom that it's not really worth
the trouble to backport these kinds of fixes, as long as it's just a
cosmetic typo.
-Neil
Neil Conway wrote:
Thomas F.O'Connell wrote:
There is a reference to the "sql_interitance" configuration in the
7.4.x docs:Since it's fixed in HEAD, I think we're fine -- we usually don't
bother applying documentation fixes to release branches, even if
there were plans for another 7.4.x release.
I was under the impression that we usually do. Time permitting, of
course.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
On Friday 10 September 2004 04:56, Peter Eisentraut wrote:
Neil Conway wrote:
Thomas F.O'Connell wrote:
There is a reference to the "sql_interitance" configuration in the
7.4.x docs:Since it's fixed in HEAD, I think we're fine -- we usually don't
bother applying documentation fixes to release branches, even if
there were plans for another 7.4.x release.I was under the impression that we usually do. Time permitting, of
course.
Well, we've certainly been getting drilled to regenerate the idocs on the
website with each new release in the 7.4.x series.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Robert Treat wrote:
On Friday 10 September 2004 04:56, Peter Eisentraut wrote:
Neil Conway wrote:
Thomas F.O'Connell wrote:
There is a reference to the "sql_interitance" configuration in
the 7.4.x docs:Since it's fixed in HEAD, I think we're fine -- we usually don't
bother applying documentation fixes to release branches, even if
there were plans for another 7.4.x release.I was under the impression that we usually do. Time permitting, of
course.Well, we've certainly been getting drilled to regenerate the idocs on
the website with each new release in the 7.4.x series.
Yes, that was me among others, exactly because of the above.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Well, here's a patch for select.sgml should a committer ever feel
inspired:
@@ -190,7 +190,7 @@
the default behavior. (In releases before 7.1,
<literal>ONLY</> was the default behavior.) The default
behavior can be modified by changing the
- <varname>sql_interitance</varname> configuration option.
+ <varname>sql_inheritance</varname> configuration option.
</para>
</listitem>
</varlistentry>
-tfo
On Sep 10, 2004, at 9:53 AM, Peter Eisentraut wrote:
Show quoted text
Robert Treat wrote:
On Friday 10 September 2004 04:56, Peter Eisentraut wrote:
Neil Conway wrote:
Thomas F.O'Connell wrote:
There is a reference to the "sql_interitance" configuration in
the 7.4.x docs:Since it's fixed in HEAD, I think we're fine -- we usually don't
bother applying documentation fixes to release branches, even if
there were plans for another 7.4.x release.I was under the impression that we usually do. Time permitting, of
course.Well, we've certainly been getting drilled to regenerate the idocs on
the website with each new release in the 7.4.x series.Yes, that was me among others, exactly because of the above.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/