From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: madwifi
Date: Tue, 5 Dec 2006 16:38:04 +0100 [thread overview]
Message-ID: <200612051638.04744.openembedded@hrw.one.pl> (raw)
In-Reply-To: <45758A01.1030203@linuxdevelopment.de>
Dnia wtorek, 5 grudnia 2006 16:02, Robert Wörle napisał:
> Is there a specific reason why you work with the .oz354 tree ?
> This tree is old and i think not maintained anymore ,, ( people correct
> me if am wrong )
Tree is maintained but have very small amount of changes. It should not be
used for non-OpenZaurus supported machines anyway.
I suggest using .dev for any development. .oz354x tree is used to maintain
OpenZaurus updates.
--
JID: hrw-jabber.org
OpenEmbedded developer/consultant
That must be wonderful! I don understand it at all.
next prev parent reply other threads:[~2006-12-05 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 22:02 madwifi Andrew Paulsen
2006-12-05 9:50 ` madwifi Justin Patrin
2006-12-05 14:29 ` madwifi Andrew Paulsen
2006-12-05 15:02 ` madwifi Robert Wörle
2006-12-05 15:38 ` Marcin Juszkiewicz [this message]
2006-12-05 15:41 ` madwifi Andrew Paulsen
-- strict thread matches above, loose matches on Subject: below --
2005-02-10 18:15 madwifi Ronald G. Minnich
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=200612051638.04744.openembedded@hrw.one.pl \
--to=openembedded@hrw.one.pl \
--cc=openembedded-devel@lists.openembedded.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.