All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: Cyrille Pitchen <cyrille.pitchen@atmel.com>,
	Richard Weinberger <richard@nod.at>,
	David Woodhouse <dwmw2@infradead.org>,
	MTD Maling List <linux-mtd@lists.infradead.org>,
	Boris BREZILLON <boris.brezillon@free-electrons.com>
Subject: Re: [GIT PULL] mtd: spi-nor: updates for 4.10
Date: Thu, 1 Dec 2016 10:50:15 -0800	[thread overview]
Message-ID: <20161201185015.GA69517@google.com> (raw)
In-Reply-To: <0914d553-20e2-b7e5-f16d-fb562601a4aa@denx.de>

On Thu, Dec 01, 2016 at 07:06:38PM +0100, Marek Vasut wrote:
> On 12/01/2016 06:41 PM, Brian Norris wrote:
> > On Thu, Dec 01, 2016 at 03:36:35PM +0100, Marek Vasut wrote:
> >> On 12/01/2016 03:22 AM, Brian Norris wrote:
> >>> BTW, does Marek have access to your repo, or are you planning on doing
> >>> all the merging?
> >>
> >> I'm not a big github fan, but I have access, yep.
> > 
> > Not even as a dumb git server? I can understand not appreciating the
> > web interface.
> 
> Well, it doesn't really feel right to keep kernel stuff outside of
> kernel.org , or is that OK now ? And I don't really like the EULA
> they have.

There's nothing magical about kernel.org. I see 63 github entries and 7
infradead entries in MAINTAINERS, and 12 github trees and 14 infradead
trees in linux-next.git, to name a few. There's also stuff at
freedesktop.org and probably other places. As with anything
kernel-related, it's a very distributed process, and the key is just to
have some kind of chain of trust, regardless of the storage location.

> > Anyway, nothing (except MAINTAINERS, which can be changed) requires we
> > use github. We could probably set up a shared infradead.org repo or
> > maybe even kernel.org if you'd prefer.
> 
> I have a k.org account, but then, I also don't want to cause too much fuss.

I mean, a shared one between all SPI NOR maintainers. i.e., Cyrille
would need access. I don't really know anything about kernel.org access
permissions, but if he can get on there, then by all means.

I won't bug much more about this either, but if you would rather pick
something like infradead.org, I'm sure David can help us out.

Brian

  reply	other threads:[~2016-12-01 18:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 13:19 [GIT PULL] mtd: spi-nor: updates for 4.10 Cyrille Pitchen
2016-12-01  2:22 ` Brian Norris
2016-12-01 14:36   ` Marek Vasut
2016-12-01 17:41     ` Brian Norris
2016-12-01 18:06       ` Marek Vasut
2016-12-01 18:50         ` Brian Norris [this message]
2016-12-02 13:28           ` Cyrille Pitchen
2016-12-02 13:58             ` Marek Vasut
2016-12-02 15:16               ` Boris Brezillon

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=20161201185015.GA69517@google.com \
    --to=computersforpeace@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=cyrille.pitchen@atmel.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marex@denx.de \
    --cc=richard@nod.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.