octave-maintainers
[Top][All Lists]
Advanced

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

Re: procedure for a patch/submission that involves a new m-file?


From: Rik
Subject: Re: procedure for a patch/submission that involves a new m-file?
Date: Tue, 24 Nov 2015 09:31:27 -0800

On 11/24/2015 07:07 AM, address@hidden wrote:
Subject:
procedure for a patch/submission that involves a new m-file?
From:
Nicholas Jankowski <address@hidden>
Date:
11/24/2015 05:31 AM
To:
Octave Maintainers List <address@hidden>
List-Post:
<mailto:address@hidden>
Precedence:
list
MIME-Version:
1.0
Message-ID:
<address@hidden>
Content-Type:
multipart/alternative; boundary=001a114d1cda4283040525495d1c
Message:
5

Wondering what the procedure is for submitting a bug fix that produces a new m-file rather than modifying an existing one, is the
normal routine still to prepare a patch? that would require knowing where in the octave foldertree the new file should reside, which I currently don't. (general question, but prompted by bug 45497.  file would probably be part of octave core vs. a package)

http://savannah.gnu.org/bugs/?45497



Nick,

Generally new functions would go to the patch tracker.  However, we're not doctrinaire about this and there is already a bug report for the issue.  I think it would be fine to upload your additions to that report.  There are already at least two maintainers following that report so one of them can review and commit your changes.

Cheers,
Rik

reply via email to

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