[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Update docs w.r.t. warning and strictness options.
From: |
Stefano Lattarini |
Subject: |
Re: [PATCH] Update docs w.r.t. warning and strictness options. |
Date: |
Sat, 15 Jan 2011 15:06:00 +0100 |
User-agent: |
KMail/1.13.3 (Linux/2.6.30-2-686; KDE/4.4.4; i686; ; ) |
On Saturday 15 January 2011, Ralf Wildenhues wrote:
> * Stefano Lattarini wrote on Sat, Jan 15, 2011 at 02:23:56PM CET:
> > On Saturday 15 January 2011, Ralf Wildenhues wrote:
> > > * Stefano Lattarini wrote on Sat, Jan 15, 2011 at 12:41:16PM CET:
> > > > , which in
> > > > +turn take precedence over those specified on the command address@hidden
> > > > +We're painfully aware that this last precedence sounds wrong and is
> > > > +against all the established conventions, but it's due to historical
> > > > +reasons, and presently cannot be easily changed. It might be fixed
> > > > +in a future Automake version though, so try not to rely on it.}.
> > >
> > > No. We already agreed to fixing this, so we should not document the
> > > broken behavior. We should fix it instead.
> > >
> > Wait, IMVHO this fix cannot just be in the next automake release
> > without a clear deprecation of the older behaviour first. The
> > backward-incompatibility would be too great and sharp otherwise.
> >
> > The right thing to do (again IMVHO) is implement the fix in a proper
> > master-based branch, and merge it back into master only after automake
> > 1.12 has been released. WDYT?
>
> Hmm. I would prefer to delay this decision until we have to cross that
> bridge; i.e.:
> - before we release 1.11.2, we should think about deprecation again,
> - when we have a patch to change precedence, we can try to evaluate how
> disruptive it is, and then decide whether it can go in 1.12 or 1.13.
>
> But anyway I don't want behavior that we want to change be documented
> and thus set in stone in the manual now, if it previously hasn't been
> documented. So, can we please decouple these things from the patch
> series we are discussing here?
>
Yes, of course. I'll remove the footnote, which, as you noted, can
always be re-proposed in a follow-up patch.
Regards,
Stefano
- Re: [PATCH 7/9] Warnings win over strictness in AUTOMAKE_OPTIONS., (continued)
[PATCH 8/9] Update NEWS about the warnings-over-strictness precedence., Stefano Lattarini, 2011/01/04
[PATCH 9/9] More checks on warnings/strictness precedence., Stefano Lattarini, 2011/01/04
[PATCH] Update docs w.r.t. warning and strictness options., Stefano Lattarini, 2011/01/15
Re: [PATCH v2 0/9] Explicit warning levels must always take precedence over those implied by the strictness, Stefano Lattarini, 2011/01/15