From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Eric Biggers <ebiggers@google.com>
Cc: linux-sparse@vger.kernel.org, sparse@chrisli.org
Subject: Re: Development version of sparse?
Date: Tue, 11 Oct 2016 20:38:57 +0200 [thread overview]
Message-ID: <20161011183856.GA2403@macpro.local> (raw)
In-Reply-To: <20161011172101.GA126173@google.com>
On Tue, Oct 11, 2016 at 10:21:01AM -0700, Eric Biggers wrote:
> Hi,
>
> I found that the "official" sparse repository,
> git://git.kernel.org/pub/scm/devel/sparse/sparse.git, only contains patches up
> to January 2015.
>
> There is another repository, which was more difficult to find, which contains
> some more recent patches, but only up to January 2016:
> http://git.kernel.org/pub/scm/devel/sparse/chrisl/sparse.git
>
> There have been a number of useful patches posted to the mailing list since then
> which don't appear in either repository, such as fixing the prototype for
> __builtin_object_size().
>
> Which one, if either, is currently the "official" repository for sparse? Is
> Chris L. still the maintainer?
>
> And if the official repository has changed, can we get some of the links
> updated? For example the one on
> https://sparse.wiki.kernel.org/index.php/Main_Page.
>
> Thanks,
>
> Eric
> --
Hi,
Yes, the official repository is indeed:
git://git.kernel.org/pub/scm/devel/sparse/sparse.git
I consider the other one as Chris' staging/pending tree and indeed
it contains some commits which have never been pushed to the official tree.
And since August 2015, there have been a now a bunch of patches posted on
the mailing list which haven't received any actions or comments from the
maintainer.
Yes, Chris Li is still the maintainer.
Luc Van Oostenryck
prev parent reply other threads:[~2016-10-11 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 17:21 Development version of sparse? Eric Biggers
2016-10-11 18:38 ` Luc Van Oostenryck [this message]
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=20161011183856.GA2403@macpro.local \
--to=luc.vanoostenryck@gmail.com \
--cc=ebiggers@google.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).