<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jun 22, 2016 at 7:37 PM, Ben Coman <span dir="ltr"><<a href="mailto:btc@openinworld.com" target="_blank">btc@openinworld.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br><span style="color:rgb(34,34,34)">But... its all one repository. Everyone who works on the vm in their</span><br></div></div>
personal space, doing a dozen generate/compile/commit cycles along the<br>
way, and then finally submits a worthwhile change via a pull request<br>
that is accepted, gets *all* their intermediate generated src added to<br>
the repository.<br></blockquote><div><br></div><div>Why would you commit your generated sources at all? And if you do, why would you push them to the public repo?</div><div><br></div><div>If you chose to commit the generated sources, then you should do so in a private branch that never gets published. You would cherry-pick non-src commits from that branch to a feature branch that you then publish for public consumption. That way the generated sources do not end up in the public repo.</div><div><br></div><div>This is one advantage of git over svn: "commit" does not mean "publish", you still have to "push". You can have as many branches on your own machine as you like.</div><div><br></div><div>- Bert -</div></div></div></div>