From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15916 invoked by alias); 15 May 2006 13:57:29 -0000 Received: (qmail 15906 invoked by uid 22791); 15 May 2006 13:57:28 -0000 X-Spam-Check-By: sourceware.org Received: from intranet.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.6) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 15 May 2006 13:57:27 +0000 Received: (qmail 25266 invoked from network); 15 May 2006 13:57:25 -0000 Received: from unknown (HELO ?192.168.2.5?) (sandra@127.0.0.2) by mail.codesourcery.com with ESMTPA; 15 May 2006 13:57:25 -0000 Message-ID: <44688908.2040304@codesourcery.com> Date: Mon, 15 May 2006 15:09:00 -0000 From: Sandra Loosemore User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: Eli Zaretskii CC: gdb-patches@sourceware.org Subject: Re: PATCH: copy-edit File-I/O section of manual References: <4465ED4D.4020505@codesourcery.com> <446659B7.3040306@codesourcery.com> <446730A4.60300@codesourcery.com> <4465ED4D.4020505@codesourcery.com> <446659B7.3040306@codesourcery.com> <20060514150059.GA29094@nevyn.them.org> <44676486.8090002@codesourcery.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00326.txt.bz2 Eli Zaretskii wrote: > If you can present the patch in a way that makes this big picture > show, it might help me review the patch sooner. Based on my > experience, such a presentation will need to use something other than > Diff, though. Would it help if I listed some of the changes I made? * I fixed several spelling errors; e.g., replacing "interupt" with "interrupt", "approriate" with "appropriate". * I fixed several verb tense errors, e.g. replacing "send" with "sent" in many places. * I fixed some places where an adjective was used where an adverb was required, e.g., replacing "successful" with "successfully", "reliable" with "reliably". * There were several places where commas were used incorrectly, often in combination with awkward phrasing of the sentence as a whole. I fixed these. * I fixed some other instances of awkward grammar, sentence construction, or word choice. * I moved the three sections of text I mentioned in a previous message to combine related information in one place. I updated the section menus to reflect these moves. * I changed the formatting of the sections describing individual calls to use @table instead of a mishmash of @smallexample, @exdent, and regular running text. This fixed problems with, for example, the return value descriptions being typeset as examples instead of as descriptive text in normal font. * In combination with the above, I put references to parameters in the running text in @var{} and references to function names, type names, and symbolic constants in @code{}. > You are asking me to proofread a large portion of text, instead of > concentrating on the relatively small differences. Well, you were complaining that the diffs were too big, and the "large portion" of text is only 12 pages. -Sandra