Timeline for Why one would commit changes to version control every three minutes?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2013 at 9:16 | review | Close votes | |||
| Aug 22, 2013 at 18:44 | |||||
| Aug 22, 2013 at 3:09 | answer | added | Edward Shen | timeline score: 0 | |
| Aug 20, 2013 at 17:23 | answer | added | BrandonV | timeline score: 2 | |
| Aug 19, 2013 at 20:12 | vote | accept | Arseni Mourzenko | ||
| Aug 19, 2013 at 20:02 | comment | added | Reactgular | wow. I wish I could program that fast. | |
| Aug 19, 2013 at 19:35 | answer | added | Karl Bielefeldt | timeline score: 11 | |
| Aug 19, 2013 at 19:18 | comment | added | mike30 | Are we talking about local or server commits? Source control is about creating save points. The more the better for your local repository. Pushing to the server will be less frequent due to testing and peer review. | |
| Aug 19, 2013 at 19:16 | answer | added | JB King | timeline score: 2 | |
| Aug 19, 2013 at 19:04 | answer | added | Mike Dunlavey | timeline score: 0 | |
| Aug 19, 2013 at 19:03 | comment | added | Tombatron | Because the best way to gauge developer productivity is by the number of commits. Right? | |
| Aug 19, 2013 at 18:57 | comment | added | Robert Harvey | That just looks like he committed a bunch of individual changes at once. Changes that were already done previously. | |
| Aug 19, 2013 at 18:57 | comment | added | Jimmy Hoffa | Why? To burn a hole in the source control server. | |
| Aug 19, 2013 at 18:54 | history | asked | Arseni Mourzenko | CC BY-SA 3.0 |