Front page | perl.bootstrap |
Postings from July 2000
Re: patch trail
Thread Previous
|
Thread Next
From:
Russ Allbery
Date:
July 24, 2000 16:14
Subject:
Re: patch trail
Message ID:
ylya2rt92f.fsf@windlord.stanford.edu
Steve Fink <sfink@digital-integrity.com> writes:
> In my company, I set up CVS to automatically mail out every patch to one
> of a set of -patches lists. It gives the filename, branch, and commit
> message. People now use the commit log messages as a way of explaining
> the patches, even if the explanation will look odd when viewed as part
> of a "cvs log" output.
gcc does this too, as a separate mailing list for CVS commits. INN does
this as well, as do most other major free software projects that I'm aware
of. This isn't quite the same thing as the patches list, although I agree
that it's valuable to have such a list (restricted to only mail from the
automated commit process).
The -patches list is also where anyone sends a patch that they want to
have reviewed, that they want other people to test, or the like. And
discussion of patches happens there (while discussion of more general
approaches and like happens on the main mailing list).
I personally merge them both into a single mail folder, but people who
don't want to get the often huge patch mail and aren't interested in
discussion of the minutia of implementation can just subscribe to the main
list and not the patches list.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
Thread Previous
|
Thread Next