From: Niklaus Giger <niklaus.giger@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-core] Re: Porting xeno-{info|load|test} to a busybox system
Date: Mon, 12 Jun 2006 23:23:36 +0200 [thread overview]
Message-ID: <e6km0o$d6p$1@domain.hid> (raw)
In-Reply-To: 448DCF9F.807@domain.hid
Jan Kiszka wrote:
<..>
> Just stumbled over this again while cleaning up my mailbox. What's the
> status? Waiting for improvements, or waiting for /someone/ to type svn
> ci (and improve the topics above later)?
Yes and no. As I told there is no urgent need to apply this before 2.2.
And improvement/more insight into the whole busybox would be a great idea.
I am busy preparing the next step for the whole xeno-test/buildbot
infrastructure, which will feature:
- Small additions to my patch for xeno-test (done)
- Buildbot will run automatically xeno-test on my PPC405 board as the last
build step (done). But it will at the moment only show, that there are
problems with my PPC405 target (see a separat thread).
- Documentation rework (mostly done)
- Adding a test script to test xeno-test (may be a overkill, but xeno-test
accumulated a lot of options, and I like unit test).
As nobody committed my patch, I will be much more confident to propose a
patch as soon as the unit tests for xeno-test work.
Best regards
---
Niklaus Giger
next prev parent reply other threads:[~2006-06-12 21:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 19:34 [Xenomai-core] Porting xeno-{info|load|test} to a busybox system Niklaus Giger
2006-05-26 13:52 ` Jan Kiszka
2006-05-26 16:52 ` Niklaus Giger
2006-05-27 16:42 ` Jan Kiszka
2006-05-28 10:00 ` Niklaus Giger
2006-05-28 10:45 ` Jan Kiszka
2006-05-28 14:41 ` Niklaus Giger
2006-05-29 11:40 ` Jan Kiszka
2006-06-06 20:32 ` Jim Cromie
2006-06-12 20:33 ` Jan Kiszka
2006-06-12 21:23 ` Niklaus Giger [this message]
[not found] ` <448DD841.1040906@domain.hid>
2006-06-14 19:01 ` Jim Cromie
2006-06-15 15:01 ` Philippe Gerum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='e6km0o$d6p$1@domain.hid' \
--to=niklaus.giger@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.