From: Samuel Bronson <naesten@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: 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: Sun, 21 Jun 2009 19:17:40 -0400 [thread overview]
Message-ID: <db65a1cd0906211617s763522f4q62952323dcbfe9d8@mail.gmail.com> (raw)
In-Reply-To: <70318cbf0906211133k55fda10exc14ca2fed4336105@mail.gmail.com>
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.
next prev parent reply other threads:[~2009-06-21 23:17 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 [this message]
2009-06-22 7:57 ` Christopher Li
2009-06-25 14:48 ` H. Peter Anvin
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=db65a1cd0906211617s763522f4q62952323dcbfe9d8@mail.gmail.com \
--to=naesten@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).