Thank you Barry. That's a good idea. If I keep my own repository so that I can have new files in my patch, would it make sense to add all eVote/Clerk's source files into the patch? I would alter mailman's "make install" to call eVote's "make install".
I see one snag, the Clerk expects a "clerk" login so I'd have to give instructions for that. Is this the most reasonable approach? Might such a big patch get put on the mailman site? eVote/Clerk is only tested on Linux. I'm quite sure won't port easily to BSD. Will this be a problem here? Marilyn On Thu, 26 Dec 2002, Barry A. Warsaw wrote: > > >>>>> "MD" == Marilyn Davis <[EMAIL PROTECTED]> writes: > > MD> I see. I was afraid of that. I don't have write-access to > MD> cvs at sourceforge, so I can't do that. > > Marilyn, another thing you might consider: create your own cvs > repository and "cvs import" the Mailman code base into it. You'd use > "cvs import" to track our changes and then you'd be able to add your > own files and generate your own "cvs diff -N" patches. > > http://www.cvshome.org/docs/manual/cvs_13.html#SEC104 > > HTH, > -Barry > _______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
