automake-patches
[Top][All Lists]
Advanced

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

Re: [PATCH] java: allow both dist_JAVA and nodist_JAVA in the same Makef


From: Stefano Lattarini
Subject: Re: [PATCH] java: allow both dist_JAVA and nodist_JAVA in the same Makefile.am
Date: Wed, 20 Apr 2011 10:29:21 +0200
User-agent: KMail/1.13.3 (Linux/2.6.30-2-686; KDE/4.4.4; i686; ; )

On Wednesday 20 April 2011, Ralf Wildenhues wrote:
> * Stefano Lattarini wrote on Wed, Apr 20, 2011 at 09:10:49AM CEST:
> > On Wednesday 20 April 2011, Ralf Wildenhues wrote:
> > > I expect to be able for some review on Friday, maybe on Thursday after
> > > that, and then hopefully on March 3.
> > >
> > I guess you mean May 3 here.
> 
> Yeah; sorry.
> 
> > What about the following middleground solution.
> 
> I trust you to do the right thing, however it looks like.  To me, the
> important bits are: the number of regressions should be as monotonically
> non-increasing as possible, and I would like to be able to review stuff
> at some point (i.e., glance at all changes, do a proper review where
> appropriate).
>
OK.  Using a new separate branch for every set of related commits that
is not an obvious bugfix or testsuite addition should help greately
with both of these bits.

> I smoke-tested FreeBSD last night, about 15 test failures.  If it helps
> you, I can spawn a full test run (which branch would you like?) tonight
> and upload logs by Friday, that should give an idea about recent
> developments.
>
Good news is that now I've a new and almost fully polished installation of
FreeBSD 8.2 myself (I had managed to mess up the previous one by an abuse
and misuse of the port system, d'oh!).  So consider that your testsuite
run might be redundant unless your FreeBSD is older than mine.  That said,
if you're going to spawn a full test run, I'd say you should do that for
the maint branch (with 1.11.2 now in sight, it would be nice if there were
no regressions nor spurious testsuite failures there).

Thanks,
  Stefano



reply via email to

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