octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44653] bolling.m in financial pkg does not us


From: Carnë Draug
Subject: [Octave-bug-tracker] [bug #44653] bolling.m in financial pkg does not use width parameter, gives incorrect result
Date: Sun, 03 May 2015 22:52:59 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Iceweasel/31.6.0

Update of bug #44653 (project octave):

                  Status:                    None => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #8:

You don't have to modify the history on the remote, you simply move back
locally to where the history diverged and continue work from there. Simply
abandon the extra heads on the remote. If you really want, you can ssh into
the SF servers with your account, and use 'hg strip' there.

Also, there's no need to make pull requests via the SF interface. It only
provides others with a list of commands to run locally to perform the merge,
but even if it supplied a merge button à la git, we wouldn't use it as we
favour a more linear history.

I have merged the four commits that fix the bug reported here as well as other
improvements. I'm closing this bug as fixed.

About the new function amerbinary, I'm still not convinced. I saw that
document you are linking before but that is on your own website and written
for you. Google gives me nothing (just non-sense pages of what can only be
automatically generated text
https://support.google.com/webmasters/answer/answer.py?answer=2721306 ) and
even scholar returns very few hits, most of them not even on journals. Maybe
I'm missing something here (probably, finance is far from my field of
research) but this doesn't seem like something that would fit on the general
finance package (if you wish to continue this discussion, it is better if we
do so on a separate bug/patch report).

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44653>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]