On Wed, Jun 08, 2016 at 06:35:21PM +0200, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > Ah yes that is more important. I'm still wondering if it should go in
> > RELEASE-NOTES as well. In our ANNOUNCE we recommend that packagers read
> > the RELEASE-NOTES file. Don't we want packagers to be
Scott Kostyshak wrote:
> Ah yes that is more important. I'm still wondering if it should go in
> RELEASE-NOTES as well. In our ANNOUNCE we recommend that packagers read
> the RELEASE-NOTES file. Don't we want packagers to be aware of this
> significant change? Or do we just assume they'll read
On Tue, Jun 07, 2016 at 10:01:04PM +0200, Jean-Marc Lasgouttes wrote:
> Le 07/06/16 à 21:45, Scott Kostyshak a écrit :
> > On Tue, Jun 07, 2016 at 08:34:59PM +0200, Georg Baum wrote:
> > > commit 273c67d8aa34a724ca03e01ae8e1792949c23297
> > > Author: Georg Baum
> > > Date: Tue Jun
Le 07/06/16 à 21:45, Scott Kostyshak a écrit :
On Tue, Jun 07, 2016 at 08:34:59PM +0200, Georg Baum wrote:
commit 273c67d8aa34a724ca03e01ae8e1792949c23297
Author: Georg Baum
Date: Tue Jun 7 20:33:06 2016 +0200
Require a C++11 compiler
As discussed on the list. If no
On Tue, Jun 07, 2016 at 08:34:59PM +0200, Georg Baum wrote:
> commit 273c67d8aa34a724ca03e01ae8e1792949c23297
> Author: Georg Baum
> Date: Tue Jun 7 20:33:06 2016 +0200
>
> Require a C++11 compiler
>
> As discussed on the list. If no C++11 compiler is found