Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #68834
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Subject | Re: Question about Source Control |
| Date | 2014-03-23 21:26 -0400 |
| References | (5 earlier) <20140322134917.080bada6@bigbox.christie.dr> <1395518482.78665.YahooMailNeo@web163804.mail.gq1.yahoo.com> <lglg0u$446$1@ger.gmane.org> <1395586700.55921.YahooMailNeo@web163806.mail.gq1.yahoo.com> <CAPTjJmpotXCzkB3NMh9xnJfCVGCeAsYpz6F4VaMA0wZKdqyJQQ@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.8429.1395624437.18130.python-list@python.org> (permalink) |
On 3/23/2014 6:56 PM, Chris Angelico wrote: > On Mon, Mar 24, 2014 at 1:58 AM, Albert-Jan Roskam <fomcl@yahoo.com> wrote: >> One more thing (so this is not entirely a double post!). While reading these books I found that the authors were pretty religious about Clean Commits. I mean, ok, it's not a good idea to do one huge monolithic commit each month, but I felt they were exaggerating. But maybe I'm wrong and clean commits become more important when the number of collaborators get bigger. It's just so easy to fix something, and e.g. correct that typo in a docstring while you're at it. >> > > It's important even with a single editor. When you go back and look at > a commit, you should be able to read the summary and know immediately > whether a particular line in it should have been edited or not. > Combining changes into a single commit makes that harder. > > Commits are cheap. Do more of 'em rather than less. With multiple branches (as with 2.7, 3.4, and default for cpython) and multiple active developers (20?) commiting to those brances, commits are definitely not free. I would not exactly call them as cheap as you seem to imply either. That said, I have occasionally pushed interim changes that put code in an improved and stable state. N. Coughlan has suggested improving the cpython infrastructure and procedures to reduce the cost of commits to encourage more people to make more commits (in the sense of more lines changed, not more pieces) and improve cpython faster. -- Terry Jan Reedy
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Question about Source Control "Frank Millman" <frank@chagford.com> - 2014-03-18 08:42 +0200
Re: Question about Source Control Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-03-19 10:51 +1300
Re: Question about Source Control Terry Reedy <tjreedy@udel.edu> - 2014-03-18 21:38 -0400
Re: Question about Source Control Tim Chase <python.list@tim.thechases.com> - 2014-03-18 21:12 -0500
Re: Question about Source Control albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-03-22 17:32 +0000
Re: Question about Source Control Tim Chase <python.list@tim.thechases.com> - 2014-03-22 13:49 -0500
Re: Question about Source Control Albert-Jan Roskam <fomcl@yahoo.com> - 2014-03-22 13:01 -0700
Re: Question about Source Control Dave Angel <davea@davea.name> - 2014-03-22 22:18 -0400
Re: Question about Source Control Albert-Jan Roskam <fomcl@yahoo.com> - 2014-03-23 07:58 -0700
Re: Question about Source Control Chris Angelico <rosuav@gmail.com> - 2014-03-24 09:56 +1100
Re: Question about Source Control Terry Reedy <tjreedy@udel.edu> - 2014-03-23 21:26 -0400
Re: Question about Source Control Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-24 01:42 +0000
Re: Question about Source Control Chris Angelico <rosuav@gmail.com> - 2014-03-24 13:04 +1100
Re: Question about Source Control Terry Reedy <tjreedy@udel.edu> - 2014-03-24 00:55 -0400
Re: Question about Source Control Chris Angelico <rosuav@gmail.com> - 2014-03-19 13:34 +1100
csiph-web