From: codesite-noreply@google.com
To: gnap-dev@lists.gentoo.org
Subject: [gnap-dev] [gnap-dev commit] r133 - wiki
Date: Mon, 04 Aug 2008 07:01:14 -0700 [thread overview]
Message-ID: <0015175d6720c6896e0453a2c5f7@google.com> (raw)
Author: jalbertosl
Date: Thu Jul 24 08:31:51 2008
New Revision: 133
Added:
wiki/GeneralRoadmap.wiki
Log:
Created wiki page through web user interface.
Added: wiki/GeneralRoadmap.wiki
==============================================================================
--- (empty file)
+++ wiki/GeneralRoadmap.wiki Thu Jul 24 08:31:51 2008
@@ -0,0 +1,23 @@
+#labels roadmap,Phase-Design
+#General roadmap and info.
+
+= Roadmap =
+
+ 1. Repos structure
+ * code (related gnap code)
+ * scripts (realted scripts)
+ * snapshots (minimal portage tree, stages and so on)
+ * portage-min
+ * portage-gnap (specific gnap ebuilds)
+ * portage-extra (some extra ebuilds)
+ * portage-sources (sources of ebuilds in portage-`*`)
+ * [min,gnap,extra] (subdirs)
+ * seedstage-uclibc (stages to use in gnap creation)
+ * seedstage-glibc
+ * gnap-core (ready to use gnap)
+ * (subdirs)
+
+ 2. Code upgrade & cleanup
+ We need to merge all the code created in last GSoC in the new repos
+
+ 3. Update portage-min
\ No newline at end of file
reply other threads:[~2008-08-04 14:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0015175d6720c6896e0453a2c5f7@google.com \
--to=codesite-noreply@google.com \
--cc=gnap-dev@lists.gentoo.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