bison-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: port some changes from master to branch-2.5


From: Joel E. Denny
Subject: Re: port some changes from master to branch-2.5
Date: Wed, 30 Dec 2009 15:08:59 -0500 (EST)
User-agent: Alpine 1.00 (DEB 882 2007-12-20)

On Wed, 30 Dec 2009, Akim Demaille wrote:

> Le 28 déc. 2009 à 04:51, Joel E. Denny a écrit :
> 
> > I'd like to push these patches to branch-2.5.  In preparation for a future 
> > patch, they port some changes from master.  I don't believe there are any 
> > other changes from master that these depend upon, but I'll wait a little 
> > while for comments before pushing just in case.
> 
> Good with me.

Thanks, I pushed them.

> There is quite some work here :( We have too many branches alive.  I'm 
> sorry I don't help more; making some releases would relieve you from 
> maintaining so many different versions.

I think we should roll 2.4.2 soon.  I can do it if you're too busy.  
However, there are at least two issues now that we should address first:

1. Florian Krohm reported a problem with %prec.  Unless there are 
objections, I'll soon push the latest solution I proposed:

  http://lists.gnu.org/archive/html/bison-patches/2009-12/msg00039.html

2. You and I have discussed putting together a survey for our users.  I 
asked gnu-prog-discuss for advice on a free survey tool with free hosting.  
So far, there haven't been any suggestions that seem to do what we need 
and still satisfy the FSF.  I later noticed that a voting system for 
Savannah is actually one of the points discussed at the latest GNU hackers 
meeting.  In summary, I'm thinking it may be a while before we find 
anything we can use.  Maybe we should just postpone the survey until after 
the 2.4.2 release.

In any case, I'm growing less inclined to ask our users for permission to 
move to C99 in the front-end.  I've been finding it difficult to resist on 
the 2.5 and master branches.  C99 is over a decade old, so I think we 
should feel free to move forward.  Of course, I understand that the 
backend is a different issue.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]