From: Michal Simek <simekm2@fel.cvut.cz>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Michal Simek <simekm2@fel.cvut.cz>, linux-kernel@vger.kernel.org
Subject: Re: New linux arch
Date: Mon, 07 Jan 2008 23:00:34 +1000 [thread overview]
Message-ID: <47822272.9090503@fel.cvut.cz> (raw)
In-Reply-To: <84144f020801070447t68808bcdq64bfc949c7732462@mail.gmail.com>
Hi Pekka,
>> Is it possible to create git repository in git.kernel.org for Microblaze
>> cpu?
>
> You need to ask the kernel.org administrators for that:
>
> http://www.kernel.org/faq/#account
Thanks.
>> How many maintainers are acceptable? (one or more)
>
> You can have as many maintainers as you want but you probably don't
> want to make it too many. There aren't any "official" responsibilities
> as a maintainer, it really depends on how much time and effort you're
> willing to put in.
OK. Don't you have idea how many linux kernels are maintained by more
people?
> You don't necessarily need a public git repository before sending your
> patches to LKML but yeah, you definitely want some public exposure
> before asking for Linus/Andrew to merge your port.
Yes.
Michal Simek
next prev parent reply other threads:[~2008-01-07 13:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 11:29 New linux arch Michal Simek
2008-01-07 12:34 ` Sam Ravnborg
2008-01-07 12:51 ` Michal Simek
2008-01-07 19:16 ` Sam Ravnborg
2008-01-07 12:47 ` Pekka Enberg
2008-01-07 13:00 ` Michal Simek [this message]
2008-01-07 13:12 ` Pekka Enberg
2008-01-07 13:34 ` Jan Engelhardt
2008-01-07 17:26 ` Stefan Richter
2008-01-07 17:39 ` Jan Engelhardt
2008-01-07 17:54 ` H. Peter Anvin
2008-01-07 18:20 ` Stefan Richter
2008-01-07 22:00 ` Benjamin Herrenschmidt
2008-01-07 22:39 ` Michal Simek
2008-01-08 8:28 ` Bryan Wu
2008-01-08 8:49 ` Pekka Enberg
2008-01-08 9:00 ` Bryan Wu
2008-01-08 17:05 ` Stefan Richter
2008-01-08 17:12 ` Stefan Richter
2008-01-09 1:16 ` Arnd Bergmann
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=47822272.9090503@fel.cvut.cz \
--to=simekm2@fel.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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