Fwd: RFC: future gfortran development and subversion

[Steve Kargl]

On Wed, Oct 19, 2005 at 10:07:41PM -0400, Kamaraju Kusumanchi wrote:
> 
> > Now, to my proposal for future gfortran development
> > post 4.1 branching.  When (if) svn becomes the source code
> > revision tool, I propose that all future work be done
> > solely on mainline.  No individual patches can be merged
> > into 4.1.  The 4.0 branch will be dead.  Periodically,
> > say bi-weekly or monthly, we do a merge from mainline
> > into 4.1.  The aim is to keep 4.1 and mainline sufficiently
> > in sync and to minimize the requirements of additional
> > hardware (except for the day or two required for the merge)
> > and to maximize our time investment.
> 
> I am just a user of gfortran (not a developer). Currently I am using
> gfortran shipped by Debian unstable. The default version offered by
> Debian unstable is gfortran 4.0 . I dont think Debian will be
> providing packages for 4.1 in the near future (1 year app). It would
> be nice if atleast some patches are ported back to 4.0 so that we
> (Debian users) need not go outside Debian to use gfortran.

I understand your position.  In fact, I use 4.0.x as my everyday
compiler.  Unfortunately, there are limited gfortran developers,
even fewer gfortran reviewers, and for myself limited hardware.
There are 2 patches from FX for mainline that I promised to
reviewed, but I've had no time to actually sit down to do the job.

I've spent the better part 5 hours search subversion's FAQ,
mailing list, and documentation for info that would give me a method
for deleting C++, java, and ada from my working copy of mainline
to recover 100s of MB of diskspace.  It *can't* be done.
When gcc switches to subversion, I will no longer hack on 
anything but mainline.

-- 
Steve