Niklaus Giger wrote:
> But I would be very interested in knowing exactly which kind of information
> the core developers are interested in. How should it be presented? In
> tabular
> form? Graphs, which ones? And kind of feedback will be evaluated and
> integrated.
I did some similar work
Jim Cromie wrote:
> perhaps as a 4th number on the version, that way xeno-config can stay as is.
>
> [EMAIL PROTECTED] bin]# ./xeno-config --version
> 2.1.50
> Id like instead:
> 2.1.50.941
>
> This seems better than pokinh around a filesystem, looking for the
> xenomai svn
> (which ma
Jim Cromie wrote:
> The -M option works, since I just received an email Id sent earlier,
> but I also sent one to xenomai-core, and it hasnt shown up yet.
In order to avoid spam, the xenomai-core list probably only accept mail
from registered members.
--
Niklaus Giger wrote:
Hi
Following a suggestion from Philippe Gerum I propose to collect and prepare
like this:
a) Make it easy to collect information
add -s/-c option to xeno-test, help text would look like
-s send output of xeno-test to [EMAIL PROTECTED]
-c if -s, send also kern
Niklaus Giger wrote:
> Hi
>
> Following a suggestion from Philippe Gerum I propose to collect and prepare
> like this:
>
> a) Make it easy to collect information
>
> add -s/-c option to xeno-test, help text would look like
> -s send output of xeno-test to [EMAIL PROTECTED]
> -c if -s
Hi
Following a suggestion from Philippe Gerum I propose to collect and prepare
like this:
a) Make it easy to collect information
add -s/-c option to xeno-test, help text would look like
-s send output of xeno-test to [EMAIL PROTECTED]
-c if -s, send also kernel config file to [EMAIL
