Re: Merging 'yacc-work' into master

[Peter Rosin]

Stefano Lattarini skrev 2012-02-13 18:54:
> On 02/13/2012 04:28 PM, Peter Rosin wrote:
>> Ah well, sorry for the noise (but some of the typos
>> could still be picked out of that patch I suppose).
>>
> Yes.  Will you do that, or should I?  If you do, the resulting patch
> is pre-approved of course.

I pushed the below to yacc-work.

I tried to merge it into yl-work-for-master as well but couldn't
figure out the merge conflict in NEWS in a reasonable amount of
time.  Go figure...

Cheers,
Peter

>From 9eb0a863f96e790ba39f7fa1c117dd88c56ed815 Mon Sep 17 00:00:00 2001
From: Peter Rosin <address@hidden>
Date: Mon, 13 Feb 2012 16:38:48 +0100
Subject: [PATCH] news: fix grammaros related to Yacc

* NEWS: Fix some grammaros and typos.
---
 NEWS |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/NEWS b/NEWS
index 8fae2dd..602dbeb 100644
--- a/NEWS
+++ b/NEWS
@@ -105,13 +105,13 @@ New in 1.11.0a:
 
   - C source and header files derived from non-distributed Yacc and/or
     Lex sources are now removed by a simple "make clean" (while they were
-    previously removed only "make maintainer-clean").
+    previously removed only by "make maintainer-clean").
 
   - Slightly backward-incompatible change, relevant only for use of Yacc
     with C++: the extensions of the header files produced by the Yacc
-    rules are now modelled after extension of the sources corresponding
+    rules are now modelled after the extension of the corresponding
     sources.  For example, yacc files named "foo.y++" and "bar.yy" will
-    produce header files named respectively "foo.h++" and "bar.hh", where
+    produce header files named "foo.h++" and "bar.hh" respectively, where
     they would have previously produced header files named simply "foo.h"
     and "bar.h".  This change offers better compatibility with `bison -o'.
 
-- 
1.7.5.1