From: "Andrey Falko" <ma3oxuct@gmail.com>
To: gnap-dev@lists.gentoo.org
Subject: Re: [gnap-dev] Steps to GNAP 3
Date: Mon, 26 May 2008 10:45:12 -0400 [thread overview]
Message-ID: <350fc7cf0805260745o5c4decc5v3ee2fc4ae8d5f0d5@mail.gmail.com> (raw)
In-Reply-To: <1211790324.1265.22.camel@supercoco>
On Mon, May 26, 2008 at 4:25 AM, josé Alberto Suárez López
<bass@gentoo.org> wrote:
> Now we have the new repos (svn) on google we can start the fun:
>
> 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
>
> 4. we need to meet (on irc)
Is everyone free June 7th 1700 GMT? (Or some other time on June 7th)
>
> any comment is welcome
Thank you for this outline! It has helped me see that big picture. If
you don't mind, I'll create a wiki page in the Google repository with
this outline..
>
> PD: please if you are interested in but don't have any comment just say
> hi to know you are alive :)
>
> --
> gnap-dev@lists.gentoo.org mailing list
>
>
prev parent reply other threads:[~2008-05-26 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 8:25 [gnap-dev] Steps to GNAP 3 josé Alberto Suárez López
2008-05-26 14:45 ` Andrey Falko [this message]
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=350fc7cf0805260745o5c4decc5v3ee2fc4ae8d5f0d5@mail.gmail.com \
--to=ma3oxuct@gmail.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