From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Council manifesto of sping
Date: Mon, 21 Jun 2010 23:36:50 +0200 [thread overview]
Message-ID: <4C1FDB72.3020609@gentoo.org> (raw)
In-Reply-To: <AANLkTiktRXmwWLkiFIQBN-ktb22utMahwxxOEtRDppdR@mail.gmail.com>
Arun,
On 06/21/10 21:25, Arun Raghavan wrote:
>> My manifesto up here now:
>> http://dev.gentoo.org/~sping/council-manifesto-2010-sping.txt
>
> For all your points where you do not have a concrete proposal of how
> you intend to tackle the problem, could you please elaborate?
please take your time to formulate concrete questions.
> """ (w.r.t. git migration)
> I hope to see Robin integrate me with the conversion process.
> """
>
> How have you contributed to the effort thus far?
I would like to re-phrase this question to
"how come you are able to help", okay?
I have
- knowledge of Git beyond an average user of Git
- migrated Portage from Subversion to Git
including explaining fake merges using commit-tree
to the portage developers [1] and more general essentials
before that [2]
- helped tommy of sunrise to get his earler multilib fork into
the Portage repo
- worked with
- Git hooks
- Gitosis
- Gitolite (including its setup)
- studied ciabot integration recently
- read most of gentoo-scm
- exchanged ideas with rbu and idl0r about it
If Robin and I reach a point of consensus on the migration's future I
could work the full rest of this week on the Git migration.
Not because we have elections right now but because I have a bit of
flexibility on the date of my next exam: pushing that a week further is
no problem at the moment.
Best,
Sebastian
[1]
http://archives.gentoo.org/gentoo-portage-dev/msg_697d7da6aca2012bce8609d59d33a7c8.xml
[2]
http://archives.gentoo.org/gentoo-portage-dev/msg_14c474fb79ee175a228e42103db9f884.xml
next prev parent reply other threads:[~2010-06-21 21:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 19:56 [gentoo-dev] Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-19 21:06 ` [gentoo-dev] Manifesto for council election Tony "Chainsaw" Vroon
2010-06-20 11:19 ` [gentoo-dev] My Council manifest Petteri Räty
2010-06-20 13:47 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-21 16:33 ` [gentoo-dev] Council manifesto of sping Sebastian Pipping
2010-06-21 18:20 ` Petteri Räty
2010-06-21 21:07 ` Sebastian Pipping
2010-06-21 19:25 ` Arun Raghavan
2010-06-21 21:36 ` Sebastian Pipping [this message]
2010-06-22 1:46 ` Brian Harring
2010-06-22 2:37 ` Sebastian Pipping
2010-06-22 5:13 ` Arun Raghavan
2010-06-22 10:02 ` [gentoo-dev] " Duncan
2010-06-22 10:24 ` Arun Raghavan
2010-06-30 0:45 ` [gentoo-dev] " Sebastian Pipping
2010-07-02 14:23 ` Arun Raghavan
2010-07-02 15:50 ` Sebastian Pipping
2010-07-02 17:30 ` Nirbheek Chauhan
2010-06-22 5:15 ` Arun Raghavan
2010-06-22 2:37 ` Alec Warner
2010-06-21 19:10 ` [gentoo-dev] My council manifesto Mark Loeser
2010-06-21 19:15 ` Arun Raghavan
2010-06-21 19:27 ` Mark Loeser
2010-06-21 19:30 ` Arun Raghavan
2010-06-21 21:19 ` [gentoo-dev] Gentoo Council 2010/2011 - Voting Mike Frysinger
2010-07-02 22:32 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting - Reminder Roy Bamford
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=4C1FDB72.3020609@gentoo.org \
--to=sping@gentoo.org \
--cc=gentoo-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