[[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
Thanks for explaining the overall background clearly. But you metioned a side issue that I suspect may refer to some important background point that I don't know. > The term was coined > when git was written, and heavily used by large projects like Linux. > It's almost like the patch+mailing list workflow, except you only need > to send one email instead of 20 patches. I am puzzled by the idea of comparing number of emails with number of patches. Why would those two numbers be related in any particular way? One can put any number of diffs, for any number of source files, into a single email, or separate them into any number of emails. So if people prefer to send everything anout a proposed change in just one email, why isn't that trivially simple? I have a hunch that relates to some constraint or complication that has not been mentioned. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)
