From: Johannes Berg <johannes@sipsolutions.net>
To: Jeff Layton <jlayton@redhat.com>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: sparse releases
Date: Tue, 15 Nov 2016 15:53:34 +0100 [thread overview]
Message-ID: <1479221614.12007.37.camel@sipsolutions.net> (raw)
In-Reply-To: <1479219687.2547.20.camel@redhat.com> (sfid-20161115_152132_102579_99F7E0F1)
On Tue, 2016-11-15 at 09:21 -0500, Jeff Layton wrote:
> I have been maintaining the fedora sparse package for a few years now
> and have been simply updating the package when there are releases. It
> looks though like there haven't been any releases in the last couple
> of
> years.
>
> Are sparse releases even "a thing" these days? Should I be revving
> the package from regular git pulls instead? I'd like to see the
> package get updates a little more regularly and am just trying to
> sort out how to do that.
Sadly, it seems that even the git tree is updated much less - and there
are a lot of pending patches. Perhaps there needs to be a maintainer
group/team?
johannes
prev parent reply other threads:[~2016-11-15 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 14:21 sparse releases Jeff Layton
2016-11-15 14:53 ` Johannes Berg [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=1479221614.12007.37.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jlayton@redhat.com \
--cc=linux-sparse@vger.kernel.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).