Bug 36375

On Wed, Mar 27, 2002 at 06:55:05PM +0200, Nevermind wrote:
>  
>  	<para>&os.stable; is our development branch from which major releases
> -	  are made.  Changes go into this branch at a different pace, and
> +	  are made.  Changes go into this branch at a different place, and
>  	  with the general assumption that they have first gone into
>  	  &os.current; first for testing.  This is <emphasis>still</emphasis>
>  	  a development branch, however, and this means that at any given time,

I think "pace" is the appropriate noun here.

Ceri

-- 
keep a mild groove on

On Wed, 27 Mar 2002 18:55:05 +0200 (EET)
Nevermind <never@nevermind.kiev.ua> wrote:

> 
> >Number:         36375
> >Category:       docs
> >Synopsis:       [PATCH] typo in
> >doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
> >Confidential:   no Severity:       non-critical
> >Priority:       low
> >Responsible:    freebsd-doc
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          doc-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Wed Mar 27 09:00:08 PST 2002
> >Closed-Date:
> >Last-Modified:
> >Originator:     Nevermind
> >Release:        FreeBSD 4.5-STABLE i386
> >Organization:
> Net.Style Ltd.
> >Environment:
> System: FreeBSD mile.nevermind.kiev.ua 4.5-STABLE FreeBSD 4.5-STABLE
> #0: Sat Mar 23 13:57:09 EET 2002
> root@mile.nevermind.kiev.ua:/usr/obj/usr/src/sys/mile i386
> 
> 
> >Description:
> 	Typo in
> 	doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml, 
> 	should be 'place' instead of 'pace'.
> 
> >How-To-Repeat:
> 	Look at
> 	doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml>
> 	Fix:
> 
 Index: chapter.sgml
 ===================================================================
 RCS file:
 /usr/home/ncvs/doc/en_US.ISO8859-1/books/handbook/cutting-edge/chap
 ter.sgml,v retrieving revision 1.112
 diff -u -r1.112 chapter.sgml
 --- chapter.sgml	22 Mar 2002 14:50:30 -0000	1.112
 +++ chapter.sgml	27 Mar 2002 16:51:29 -0000
 @@ -331,7 +331,7 @@
  	<indexterm><primary>-STABLE</primary></indexterm>
  
      <para>&os.stable; is our development branch from which major
releases-	are made.  Changes go into this branch at a different pace,
and+	are made.  Changes go into this branch at a different place, and
	with the general assumption that
  	they have first gone into  &os.current; first for testing. 
  	This is <emphasis>still</emphasis>  a development branch,
  	however, and this means that at any given time,
> 

I think what the original author is trying to say is:

pace > different pace > different time and a different way.

and place would be a different spot.  What do you think?

Thanks alot for the submission though
-- 
Tom (Darklogik) Rhodes
www.FreeBSD.org  -The Power To Serve
www.Pittgoth.com -Pittgoth Discussion Portal
trhodes@ {Pittgoth.com, FreeBSD.org}

Hello, Tom Rhodes!

On Wed, Mar 27, 2002 at 12:32:39PM -0500, you wrote:

> > >Number:         36375
> > >Category:       docs
> > >Synopsis:       [PATCH] typo in
> > >doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
[snip]
> I think what the original author is trying to say is:
> 
> pace > different pace > different time and a different way.
> 
> and place would be a different spot.  What do you think?
Yes, you are right, I misunderstood author's idea :)
Please, close this PR.

-- 
NEVE-RIPE

Comment 4 Ceri Davies 2002-03-27 20:05:27 UTC

State Changed
From-To: open->closed



Originator agrees that the current text accurately reflects 
the authors' intentions.

Comment 5 Giorgos Keramidas 2002-03-27 22:47:04 UTC

On 2002-03-27 18:55, Nevermind wrote:

> >Description:
> 	Typo in doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,
> 	should be 'place' instead of 'pace'.

Well, I think the original author meant to use "rate" instead of "place",
in an effort to emphasize on the relative "stability" of the STABLE
branches, and the smaller number of commits that are in general expected to
happen in the STABLE branch, compared to the "lively" state of the HEAD
branch where CURRENT lives.

If the original text seems confusing, I'll agree that it needs to be made
as clear as possible though.  In Michael Lucas' spirit, we need to make it
``impossible for the reader to misunderstand what is written.''

Giorgos Keramidas                       FreeBSD Documentation Project
keramida@{freebsd.org,ceid.upatras.gr}  http://www.FreeBSD.org/docproj/