* sparse releases
@ 2016-11-15 14:21 Jeff Layton
2016-11-15 14:53 ` Johannes Berg
0 siblings, 1 reply; 2+ messages in thread
From: Jeff Layton @ 2016-11-15 14:21 UTC (permalink / raw)
To: Sparse Mailing-list
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.
Thanks,
--
Jeff Layton <jlayton@redhat.com>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: sparse releases
2016-11-15 14:21 sparse releases Jeff Layton
@ 2016-11-15 14:53 ` Johannes Berg
0 siblings, 0 replies; 2+ messages in thread
From: Johannes Berg @ 2016-11-15 14:53 UTC (permalink / raw)
To: Jeff Layton, Sparse Mailing-list
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-11-15 14:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-11-15 14:21 sparse releases Jeff Layton
2016-11-15 14:53 ` Johannes Berg
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).