On 01/01/2018 01:00 PM, sysvinit-devel-requ...@nongnu.org wrote: > Send Sysvinit-devel mailing list submissions to > sysvinit-devel@nongnu.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.nongnu.org/mailman/listinfo/sysvinit-devel > or, via email, send a message with subject or body 'help' to > sysvinit-devel-requ...@nongnu.org > > You can reach the person managing the list at > sysvinit-devel-ow...@nongnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Sysvinit-devel digest..." > > > Today's Topics: > > 1. Re: Checking for a pulse (Petter Reinholdtsen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 01 Jan 2018 08:13:44 +0100 > From: Petter Reinholdtsen <p...@hungry.com> > To: sysvinit-devel@nongnu.org > Subject: Re: [sysvinit-devel] Checking for a pulse > Message-ID: <2flincmrqzb....@diskless.uio.no> > Content-Type: text/plain > > [Jesse Smith] >> Thanks very much for accepting me on board. Is there a review process >> for accepting new patches/changes? I've been working on a handful of >> minor issues and would like to get them looked at/approved. Right now >> all my changes have been uploaded to the GitHub account under the >> Savannah branch (see above), but if this group has another approved way >> to share patches I'll use it. > Not really. There is a coverity check that would be good to use to > ensure no regressions are introduced, but that is about it. > > Perhaps a good start is to migrate sysvinit upstream to git? >
I think switching to git makes sense. The source tree as it is, with the "tags" and "trunk" directories, is fairly easy to navigate but maybe redundant? Long term, git will probably make merging patch sets from various distros easier. Plus, once we have an official git upstream I should be able to simply import my branch for people to test. - Jesse
