On Mon, Sep 14, 2015 at 06:06:02PM +0100, Szabolcs Nagy wrote:
> On 14/09/15 17:58, Rich Felker wrote:
> >trunk. For the ChangeLog message, do I need to list both configure and
> >configure.ac or just the latter? And should configure be included in
> >the patch like I did, or regenerated when the p
On 14/09/15 17:58, Rich Felker wrote:
trunk. For the ChangeLog message, do I need to list both configure and
configure.ac or just the latter? And should configure be included in
the patch like I did, or regenerated when the patch is applied?
list both
i think it's ok to fix configure manually
On Mon, Sep 14, 2015 at 07:08:33AM +0900, Kaz Kojima wrote:
> Rich Felker wrote:
> > I'm pretty sure this will still apply to trunk, but I can check that
> > and add the changelog entry. Is there something I should read on the
> > form or just follow the example from my last patch where you added
Rich Felker wrote:
> I'm pretty sure this will still apply to trunk, but I can check that
> and add the changelog entry. Is there something I should read on the
> form or just follow the example from my last patch where you added it?
The latter would be enough for this, though
https://gcc.gnu.or
On Sun, Sep 13, 2015 at 06:55:56PM +0900, Kaz Kojima wrote:
> Rich Felker wrote:
> > Bad patterns caused configure to always disable TLS for big-endian sh
> > targets and for anything other than sh 3/4.
>
> Could you please give a patch for the trunk with an appropriate
> ChangeLog entry?
I'm pr
Rich Felker wrote:
> Bad patterns caused configure to always disable TLS for big-endian sh
> targets and for anything other than sh 3/4.
Could you please give a patch for the trunk with an appropriate
ChangeLog entry?
Regards,
kaz
