From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Re: Your part on ideas/issues for Google Summer of Code 2010
Date: Fri, 05 Mar 2010 16:43:43 +0100 [thread overview]
Message-ID: <4B9126AF.5050009@gentoo.org> (raw)
In-Reply-To: <4B9094B0.2070509@gentoo.org>
On 03/05/10 06:20, Zac Medico wrote:
> On 03/03/2010 04:03 PM, Sebastian Pipping wrote:
>> @zmedico
>> implement a bunch of repoman checks
>> http://bugs.gentoo.org/buglist.cgi?quicksearch=repoman
>
> I'm not sure if that's appropriate for a SOC project because it's
> like a bunch of independent small projects that could easily be done
> by separate individuals. My idea of a SOC project is something that
> absolutely requires the sustained focus of a single individual.
It's not a perfect fit, right.
Alternatively we could use these repoman check bugs to get more people
into the portage boat once we're on Git with it.
>> Native Portage Multilib Support?
>> http://bugs.gentoo.org/show_bug.cgi?id=145737
>
> It's already been done:
>
> http://wiki.github.com/sjnewbury/multilib-overlay/
>
> It seems like all we need to do now is finalize the details and put
> together a migration plan for integrating it into Gentoo.
Please update the bug accordingly and make sure it doesn't "get lost".
Sebastian
next prev parent reply other threads:[~2010-03-05 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 0:03 [gentoo-soc] Your part on ideas/issues for Google Summer of Code 2010 Sebastian Pipping
2010-03-04 7:13 ` [gentoo-soc] " Hans de Graaff
2010-03-26 22:18 ` Sebastian Pipping
2010-03-04 7:17 ` [gentoo-soc] " Arun Raghavan
2010-03-04 7:52 ` Nirbheek Chauhan
2010-03-05 0:21 ` Sebastian Pipping
2010-03-05 0:22 ` Sebastian Pipping
2010-03-05 6:21 ` Nirbheek Chauhan
2010-03-05 6:26 ` Nirbheek Chauhan
2010-03-28 18:15 ` Hans de Graaff
2010-03-05 5:20 ` [gentoo-soc] " Zac Medico
2010-03-05 15:43 ` Sebastian Pipping [this message]
2010-03-06 0:51 ` Zac Medico
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=4B9126AF.5050009@gentoo.org \
--to=sping@gentoo.org \
--cc=gentoo-soc@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