On Thu, May 7, 2015 at 9:05 AM, Mike Hearn <m...@plan99.net> wrote: > Maybe you dislike that idea. It's so .... centralised. So let's say Gavin > commits his patch, because his authority is equal to all other committers. > Someone else rolls it back. Gavin sets up a cron job to keep committing the > patch. Game over. > > You cannot have committers fighting over what goes in and what doesn't. > That's madness. There must be a single decision maker for any given > codebase.
Hmm, git repositories don't quite work like that. Instead, you should imagine everyone having a local copy of the git repository. Each developer synchronizes their git repository with other developers. They merge changes from specific remote branches that they have received. Each developer has their own branch and each developer is the "single decision maker" for the artifact that they compile. - Bryan http://heybryan.org/ 1 512 203 0507 ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
