From: Cort Dougan <cort@fsmlabs.com>
To: Ira Weiny <iweiny@acm.org>
Cc: linxuppc-emb <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: linuxppc_2_5 source tree (and others)
Date: Mon, 14 May 2001 19:40:03 -0600 [thread overview]
Message-ID: <20010514194003.C12060@ftsoj.fsmlabs.com> (raw)
In-Reply-To: <3AFEE17F.6A59CB1F@acm.org>; from iweiny@acm.org on Sun, May 13, 2001 at 12:33:19PM -0700
Nope. The _devel tree does mean it's a development tree with experimental
changes in it. It will sometimes work, sometimes not.
The _2_4 tree will contain the changes we're more confident in and have
tested somewhat.
Only the _2_4_devel tree has the Walnut changes right now.
} Are these trees designed to work "out of the box" on boards such as the
} Walnut?
}
} When configuring I don't see any options for the specific 405GP ethernet
} for instance.
For read-only access, no password is necessary. I fixed the rsync problem,
it's working now.
} Also, do I need a password or something to get the devel tree? Am I
} allowed to get to the devel tree?
}
} As per the instructions on the page (adding -azv):
}
} $ rsync -azv bitkeeper.fsmlabs.com::linuxppc_2_4_devel
} linuxppc_2_4_devel
} @ERROR: Unknown module 'linuxppc_2_4_devel'
} $ rsync bitkeeper.fsmlabs.com::
} linuxppc_2_2
} linuxppc_2_4
} $
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-15 1:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 18:40 linuxppc_2_5 source tree (and others) Albert D. Cahalan
2001-05-10 18:49 ` Tom Rini
2001-05-10 19:46 ` Albert D. Cahalan
2001-05-10 19:57 ` Cort Dougan
2001-05-10 21:24 ` Albert D. Cahalan
2001-05-10 23:11 ` Cort Dougan
2001-05-11 2:31 ` Murray Jensen
2001-05-11 3:14 ` Cort Dougan
2001-05-11 5:43 ` Murray Jensen
2001-05-10 21:44 ` Tom Rini
2001-05-13 19:33 ` Ira Weiny
2001-05-15 1:40 ` Cort Dougan [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-10 8:38 Murray Jensen
2001-05-10 16:10 ` Tom Rini
2001-05-10 16:24 ` Dan Malek
2001-05-10 19:33 ` Cort Dougan
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=20010514194003.C12060@ftsoj.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=iweiny@acm.org \
--cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).