[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #38460] Option 'stable' missing from unique()
|
From: |
Jordi Gutiérrez Hermoso |
|
Subject: |
[Octave-bug-tracker] [bug #38460] Option 'stable' missing from unique() |
|
Date: |
Thu, 07 Mar 2013 18:22:40 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 |
Update of bug #38460 (project octave):
Status: None => Confirmed
_______________________________________________________
Follow-up Comment #4:
Okay, I rebased your patch and edited the commit message a little:
http://hg.savannah.gnu.org/hgweb/octave/rev/1f1e248caeab
You may wish to remove your original local copy of this patch with
hg strip -r e014f0449eda8
I'm leaving this bug report open, since the issue of "stable" being
unimplemented is still open.
By the way, TMW has changed how unique.m presents its output, and has added
the quite horrible "legacy" and "2012a" options to switch between these two.
I'm not sure what Octave should do about this.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?38460>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/