On Tue, Aug 30, 2016 at 01:15:20PM +0200, Laurent Bercot wrote: > >I will be happy to send a 0/n introductory message (git send-email > >--compose) for any future proposed series, i was not aware that was the > >custom here. Indeed, i wrote this series because i could find no clear > >instructions for how to propose improvements to runit's codebase. > > I'm not sure. This is more of a discussion/questions list than a > patch-sending list; as far as I'm concerned I don't like to receive > patches without some discussion before or at least a little context, but > for runit you'd have to check with the new runit maintainer, if there's > one - Gerrit, before you leave, please designate one, and if the answer > is "it's maintained by Debian/whateverdistro these days", then we'll know > the right place to send patches is the Debian/whateverdistro ML (but the > actual maintainers should still subscribe to our list and read it).
Hi, I'm not leaving, just getting older.. Although runit now has a new Debian maintainer, I intend to keep my hands on the runit original upstream package, most probably not applying many changes to it, if at all. I consider it very stable and usable. There's one itch https://bugs.debian.org/641632 actually reported by Daniel back then. A proposed patch is available in the devground branch in the git repository. But with this bug we're actually living for years already, seems to happen very rarely. > >Alternately, if there's a better way to propose changes than sending > >mail to this list, i'd be happy to rewrite code.html to document it, but > >i don't know what it is. > > I'm sorry I don't have a clearer answer. Until we know more precisely how > the future of runit is organized, it's kinda in a limbo state. I'm not against patches to runit, as long as submitters are not demotivated by the fact that it may take some time for me to respond, and probably most of the patches won't make it into my git repository. As I did contributions to git end of 2005 and the years after that, I'd be fine with submitting patches through the mailing list, as they still do. OTOH there's some discussion about the development workflow through mailboxes on the git list lately https://marc.info/?t=147136665300005&r=1&w=2 Regards, Gerrit.