Re: [OctDev] Inconsistency in how packages are rolled out

2011-04-19 Thread Andy Buckle
On Wed, Apr 20, 2011 at 12:56 AM, Stephen Montgomery-Smith wrote: > So when a new package is rolled out, for example bim-1.0.1.tar.gz, when > you untar it, it is unpredictable whether the directory created is > called "bim" or "bim-1.0.1."  Some packages use the former name > convention, some pack

[OctDev] Inconsistency in how packages are rolled out

2011-04-19 Thread Stephen Montgomery-Smith
So when a new package is rolled out, for example bim-1.0.1.tar.gz, when you untar it, it is unpredictable whether the directory created is called "bim" or "bim-1.0.1." Some packages use the former name convention, some packages use the latter. As the FreeBSD maintainer of the octave-forge-* po

[OctDev] nancumsum in package nan?

2011-04-19 Thread Muhali
I guess the subject says it all. M. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simpli

Re: [OctDev] request to register as a developer

2011-04-19 Thread L. Markowsky
Subject: Re: [OctDev] request to register as a developer From: w4nderl...@gmail.com Date: Sun, 17 Apr 2011 20:59:33 +0200 CC: carlo.defa...@gmail.com; pio.gianv...@gmail.com To: lmar...@users.sourceforge.net Hello, sorry i misread, you told you had no need to implement fuzzy set theory op

Re: [OctDev] request to register as a developer

2011-04-19 Thread L. Markowsky
> Subject: Re: [OctDev] request to register as a developer > From: carlo.defa...@gmail.com > Date: Mon, 18 Apr 2011 23:53:38 +0200 > CC: w4nderl...@gmail.com; octave-dev@lists.sourceforge.net; > pio.gianv...@gmail.com > To: lmar...@users.sourceforge.net > > > On 18 Apr 2011, at 23:17, L. Markow

[OctDev] error in arburg function reference

2011-04-19 Thread Hugh Brunk
The arburg function reference is currently: RETURNED VALUES: a %% [polynomial/vector] list of (P+1) autoregression coeffic- %% ients; for data input x(n) and white noise e(n), %% the model is %% P+1

Re: [OctDev] kleening up list of active developers

2011-04-19 Thread Peter Lanspeary
Carlo, I would like my developer status to remain active, please. At the very least, I wish to improve a number of sigproc functions when I can find time. Thanks, Peter On Tue, Apr 19, 2011 at 04:54:13PM +0200, c. wrote: > > Ok, I decided to be more conservative and checked (using the very hand

Re: [OctDev] kleening up list of active developers

2011-04-19 Thread c.
On 19 Apr 2011, at 09:52, Søren Hauberg wrote: > man, 18 04 2011 kl. 21:48 +0200, skrev Carlo de Falco: >> I remember David used to periodically check the list of octave-forge >> developers in order to disable >> those that had been inactive for a long time and keep the total number of >> devel

Re: [OctDev] kleening up list of active developers

2011-04-19 Thread Carnë Draug
2011/4/19 Carnë Draug : > 2011/4/19 c. : >> Do you think it would be possible to modify it >>  so that it lists users that did NOT commit since a given date? > > If you can give me (or a command that gives me) a list of all users, > yes with no problem at all. Otherwise it would have to check all >

Re: [OctDev] kleening up list of active developers

2011-04-19 Thread Carnë Draug
2011/4/19 c. : > Do you think it would be possible to modify it > so that it lists users that did NOT commit since a given date? If you can give me (or a command that gives me) a list of all users, yes with no problem at all. Otherwise it would have to check all commits from revision 1 in order t

Re: [OctDev] kleening up list of active developers

2011-04-19 Thread c.
On 19 Apr 2011, at 02:05, Carnë Draug wrote: > On 18 April 2011 20:48, Carlo de Falco wrote: >> Does anyone know how to easily get activity info for all registered >> developers in order to select those that can be considered inactive? > > I just wrote a perl tiny script that lists all the use

Re: [OctDev] kleening up list of active developers

2011-04-19 Thread Søren Hauberg
man, 18 04 2011 kl. 21:48 +0200, skrev Carlo de Falco: > I remember David used to periodically check the list of octave-forge > developers in order to disable > those that had been inactive for a long time and keep the total number of > developers limited. > > I think that was a good idea and we