David Lichteblau <[email protected]> writes: > Quoting Nicolas Neuss ([email protected]): >> I keep seeing only mails reporting issues on this list, but no reaction >> from any maintainer. I would be interested in who is maintaining >> clbuild and if (s)he is still active/alive? > > I'm alive, but I don't have much time to spend on clbuild. > > What that means is that I'm trying to merge patches, but I can only do > so if it's very easy for me. > > "Very easy" for me are patches that are arriving as pull requests, i.e. > > 1. The patch submitter records the patch using darcs > > 2. Publishes his repository on any webserver > > 3. Sends mail to the list, pointing to the repository, requesting > that patches be pulled and moved over to the main repository > > 4. The patch must not include changes to the 'dependencies' file, > because that is being autogenerated in a separate step. > > (A separate patch to dependencies is fine, I can skip that.) > > 5. Each patch should be self-contained, i.e. must not change two > projects at once. > > Anyone following these steps has a good chance that I'll type "darcs > pull" and try those patches. > > Anything else (inline patches, lists of URLs, ...) is unlikely to get my > attention. > > > I know that the webpage doesn't have the full instructions and just says > something like "send a note to the list", but unfortunately that's > outdated.
So sounds like someone could step up and create/maintain a patch queue for you. -T. _______________________________________________ clbuild-devel mailing list [email protected] http://common-lisp.net/cgi-bin/mailman/listinfo/clbuild-devel
