On 04/11/16 09:16, David Bariod wrote:

On Fri, Nov 4, 2016 at 9:55 AM, Chris Jones <jon...@hep.phy.cam.ac.uk
<mailto:jon...@hep.phy.cam.ac.uk>> wrote:

    On 04/11/16 05:39, David Bariod wrote:


        Personnally, I would just commit such change. It is cheap, can be
        reworked later and be ketp safe in a private remote repository
        in case
        of disaster.
        With git there are no reason to not commit event not ready yet
        change set.

    I would not do this, as you then might end up with a lot of
    intermediary commits in the history. better I think to work on
    independent projects on independent branches.

Then you can do a git rebase -i to clean up when you want to publish
your final state.

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.


macports-dev mailing list

Reply via email to