[Vm-dev] The code in the src folders in the repository

Bert Freudenberg bert at freudenbergs.de
Thu Jun 23 09:33:04 UTC 2016


On Wed, Jun 22, 2016 at 7:37 PM, Ben Coman <btc at openinworld.com> wrote:

>
> But...  its all one repository.  Everyone who works on the vm in their
> personal space, doing a dozen generate/compile/commit cycles along the
> way, and then finally submits a worthwhile change via a pull request
> that is accepted, gets *all* their intermediate generated src added to
> the repository.
>

Why would you commit your generated sources at all? And if you do, why
would you push them to the public repo?

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.

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.

- Bert -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20160623/aa96ca34/attachment.htm


More information about the Vm-dev mailing list