All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Samuel Bronson <naesten@gmail.com>
Cc: Christopher Li <sparse@chrisli.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-sparse@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
Date: Thu, 25 Jun 2009 07:48:00 -0700	[thread overview]
Message-ID: <4A438E20.5070704@zytor.com> (raw)
In-Reply-To: <db65a1cd0906211617s763522f4q62952323dcbfe9d8@mail.gmail.com>

Samuel Bronson wrote:
> On Sun, Jun 21, 2009 at 2:33 PM, Christopher Li<sparse@chrisli.org> wrote:
>> On Sat, Jun 20, 2009 at 12:37 PM, Samuel Bronson <naesten@gmail.com> wrote:
>>> About that ... shouldn't the URL on the sparse web page be
>>> "git://git.kernel.org/pub/scm/devel/sparse/chrisl/sparse.git", not
>>> "git://git.kernel.org/pub/scm/devel/sparse/sparse.git"?
>> I don't have permission on the sparse web page. Josh is still
>> the official maintainer. But he has been very quietly on the project recently.
>> That is the main reason I created my tree. I don't want good patch get
>> lost.
>>
>> I did not mean to fork the sparse project. I don't know how to resolve
>> it either.
> 
> Nobody is going to hold having maybe accidentally become the
> maintainer *against* you.
> Not to say you won't suffer for it -- people will always be expecting
> you to review patches and so forth -- but they won't hold it against
> you.

If there is clear consensus within the Sparse devel community that Chris
is the new maintainer, I will give him write access to the relevant
directories.  That's better than having the chrisl/ directory become
official.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  parent reply	other threads:[~2009-06-25 18:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 19:20 RFC: Move sparse.git inside linux-kernel-2.6.git? Sam Ravnborg
2009-06-18 19:34 ` Jeff Garzik
2009-06-18 19:57   ` Jeff Garzik
2009-06-18 20:13     ` Randy Dunlap
2009-06-18 20:18   ` Sam Ravnborg
2009-06-18 20:40 ` Christopher Li
2009-06-20 19:37   ` Samuel Bronson
2009-06-21 18:33     ` Christopher Li
2009-06-21 23:17       ` Samuel Bronson
2009-06-22  7:57         ` Christopher Li
2009-06-25 14:48         ` H. Peter Anvin [this message]
2009-07-02 23:21 ` Josh Triplett
2009-07-02 23:46   ` Christopher Li

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=4A438E20.5070704@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=naesten@gmail.com \
    --cc=sam@ravnborg.org \
    --cc=sparse@chrisli.org \
    --cc=torvalds@linux-foundation.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 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.