Should patches for PR target/1532 go on 3.4 branch?

[Ian Lance Taylor]

Mark Mitchell <mark@codesourcery.com> writes:

> >PR target/1532 is currently targeted at 3.4.0.  It has been fixed on
> >mainline via these patches:
> >
> >2004-02-11  Richard Henderson  <rth@redhat.com>
> >
> >2004-01-24  Ian Lance Taylor  <ian@wasabisystems.com>
> >  2004-01-24  Andreas Tobler  <a.tobler@schweiz.ch>
> >
> >
> >2004-01-23  Ian Lance Taylor  <ian@wasabisystems.com>
> >
> >I recommend that we put these patches onto the 3.4 branch.
> >
> I agree.  Please install the patches.

Done.

OK, bugmasters, what should happen now to PR target/1532?  It is
targeted at 3.4.0.  It has now been fixed for 3.4.0.  The 3.3 branch
is still open.  It is a regression for the 3.3 branch.

Giovanni said that for a regression, the PR normally stays open until
the affected branches are discontinued.  That suggests that this PR
should stay open, unless and until the release manager determines that
it will not be fixed for 3.3.

Perhaps the fact that the target has been set to 3.4.0 means that it
has already been decided that this PR will not be fixed in the 3.3
branch, and therefore we can close it now?  That would make sense to
me.

Otherwise, the problem is that I'm searching for open bugs with a
target of 3.4.0.  I don't want this bug to come up in that search any
more, since it has been fixed in 3.4.0.  It's not a huge deal, of
course, but how do we express the state ``regression for 3.3, fixed
for 3.4'' while preserving the useful search ``bugs targeted for 3.4
which have not been fixed?''

Ian