<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 23, 2016 at 5:33 PM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> <br><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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><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></div></div></blockquote><div><br></div><div>I *don't* want to commit my generated sources. But** there they are, tracked files that have been modified so I need to weed out the changes I do want to commit.</div><div><br></div><div>**Likely I'm overthinking this; its an imagined scenario. I should wait to comment further until I actually hit this scenario so at least I know which foot I'm putting in my mouth. :)</div><div><br></div><div>cheers -ben</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><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>
<br></blockquote></div><br></div></div>