From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Andreas Schwab <schwab@suse.de>, <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Fix undefined behaviour inconsistent for strtok
Date: Tue, 25 Oct 2016 13:51:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1610251346170.31520@digraph.polyomino.org.uk> (raw)
In-Reply-To: <0c863018-569b-e482-1c98-d7dd34c977f5@linaro.org>
On Tue, 25 Oct 2016, Adhemerval Zanella wrote:
> None I am aware of, but regardless it is a effort to close down old
> glibc bugs and keep the backlog under control.
Well, if a bug report is invalid then closing it as INVALID is
appropriate. Or if there is an idea in the bug report that might or might
not be a good idea but isn't appropriate for Bugzilla, closing as INVALID
and putting a note on
<https://sourceware.org/glibc/wiki/Development_Todo/Master> of the idea to
consider (with a link to the previous discussion in the bug) is
appropriate.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-10-25 13:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 10:58 Adhemerval Zanella
2016-10-25 11:31 ` Andreas Schwab
2016-10-25 12:33 ` Adhemerval Zanella
2016-10-25 12:57 ` Andreas Schwab
2016-10-25 13:13 ` Adhemerval Zanella
2016-10-25 13:20 ` Andreas Schwab
2016-10-25 13:23 ` Adhemerval Zanella
2016-10-25 13:45 ` Andreas Schwab
2016-10-25 13:49 ` Adhemerval Zanella
2016-10-25 13:51 ` Joseph Myers [this message]
2016-10-25 14:08 ` Adhemerval Zanella
2016-10-25 13:32 ` Florian Weimer
2016-10-25 14:04 Wilco Dijkstra
2016-10-25 16:46 ` Wilco Dijkstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1610251346170.31520@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).