<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 4, 2016 at 10:20 AM, Chris Jones <span dir="ltr"><<a href="mailto:jonesc@hep.phy.cam.ac.uk" target="_blank">jonesc@hep.phy.cam.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<span class=""><br>
<br>
On 04/11/16 09:16, David Bariod wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
<br>
On Fri, Nov 4, 2016 at 9:55 AM, Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk" target="_blank">jonesc@hep.phy.cam.ac.uk</a><br></span><span class="">
<mailto:<a href="mailto:jonesc@hep.phy.cam.ac.uk" target="_blank">jonesc@hep.phy.cam.ac.<wbr>uk</a>>> wrote:<br>
<br>
<br>
<br>
On 04/11/16 05:39, David Bariod wrote:<br>
<br>
Hello,<br>
<br>
Personnally, I would just commit such change. It is cheap, can be<br>
reworked later and be ketp safe in a private remote repository<br>
in case<br>
of disaster.<br>
With git there are no reason to not commit event not ready yet<br>
change set.<br>
<br>
<br>
I would not do this, as you then might end up with a lot of<br>
intermediary commits in the history. better I think to work on<br>
independent projects on independent branches.<br>
<br>
<br>
Then you can do a git rebase -i to clean up when you want to publish<br>
your final state.<br>
</span></blockquote>
<br>
Still, if you have independent pieces of work in progress, its still better IMHO to separate them into branches. The policy of not working on the master with git is not my idea, its a widely held piece of (good) advice, for various reasons.<br></blockquote><div><br></div><div>Yes, using different branch is definitely a good idea<br><br></div><div>David <br></div></div></div></div>