|
| From: | Markus Mützel |
| Subject: | [Octave-bug-tracker] [bug #59275] permission denied warning does not have an id |
| Date: | Thu, 15 Oct 2020 12:24:32 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36 Edg/86.0.622.38 |
Update of bug #59275 (project octave):
Status: None => Need Info
Release: 5.2.0 => 6.0.90
_______________________________________________________
Follow-up Comment #1:
Only a (small) subset of warnings and errors in Octave have an associated id.
I'm not opposed to adding an id to this particular warning. Just out of
curiosity: Why would you like to have an id for that particular warning?
Are there general criteria we could follow for which warnings should have an
id?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?59275>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |