On 4/11/20, Nicolas George <geo...@nsup.org> wrote: > Anton Khirnov (12020-04-11): >> It is done the way we, as a whole community, decide it is done. In >> practice, many people send ALL of their patches to the ML. > > I am with Anton on this one. Rules are not set in stone, “and even stone > changes, anyway”. > > And I think too it would be much better if all patches were submitted to > the mailing-list. To have many eyes spot small mistakes, if only typos > in the commit message. To get heads-up about possible conflicting work. > To suggests transversal enhancements, etc. > > It is not as if sending the mail and waiting a few days to push the > branch will hinder anybody's work much. And if it does, well, 2005 > called and they want their SVN habits back. > > Code maintainership is first and foremost a responsibility. It only > gives rights to sustain that responsibility. >
I own right to directly commit to any file in codebase I maintain. Because only I know such code well. Allowing various "nice" interruptions by sending patches to list is waste of everybody time. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
