mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Michal Simek" <simekm2@fel.cvut.cz>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu
Subject: Re: New linux arch
Date: Mon, 7 Jan 2008 14:47:10 +0200	[thread overview]
Message-ID: <84144f020801070447t68808bcdq64bfc949c7732462@mail.gmail.com> (raw)
In-Reply-To: <47820D24.3060800@fel.cvut.cz>

Hi Michael,

On Jan 7, 2008 1:29 PM, Michal Simek <simekm2@fel.cvut.cz> wrote:
> 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

On Jan 7, 2008 1:29 PM, Michal Simek <simekm2@fel.cvut.cz> wrote:
> What are maintainers responsibilities? Do you have any page about?
> I am  U-BOOT maintainer at denx.de and I hope that the responsibilities
> will be similar.
>
> 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.

On Jan 7, 2008 1:29 PM, Michal Simek <simekm2@fel.cvut.cz> wrote:
> I see the right way to push all changes to public git repository and
> then send patches in small logical group to LKML with CC to people from
> microblaze community.
>
> And then wait for comments from you, solve problems, update git
> repository and send changes again.

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.

                        Pekka

  parent reply	other threads:[~2008-01-07 12:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 11:29 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 [this message]
2008-01-07 13:00   ` Michal Simek
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=84144f020801070447t68808bcdq64bfc949c7732462@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=simekm2@fel.cvut.cz \
    /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

all inboxes | Powered by JetHome®