I have a request. The amount of mail on fink-commits generated by .info
and .patch file changes is rather daunting.
Could the fink-commits list be split into seperate lists for seperate
projects? At the very least could the changes to .info and .patch files be
put on a seperate list? Or a list created which doesn't have those commits?
That would make watching changes to the parts of the code you're interested
in a bit easier.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
I wanted to suggest a commit split too... (thanks for getting here first;))
What about moving 10.3 and 10.2-gcc3 commits into a new list, maybe another one for experimental directory?
Separating like this would cut the mailings in half for (what would then become) the 10.2/10.1 list. (Or separate them the other way round, whichever is the most popular)
Carsten
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
