How to keep uncommitted work in a git clone

[Michael]

On 2016-11-03, at 10:39 PM, David Bariod <davidriod at googlemail.com> wrote:

> Hello,
> 
> 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.
> 
> Best regards,
> David

I assume that last line should be "to not commit even not ready yet change sets".

I agree that you can commit anything.
But only if you follow the rule of not working/committing directly to master.
Leave your junk on a side branch, and put the fixed-up work into master later.


---
Entertaining minecraft videos
http://YouTube.com/keybounce

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20161104/e8de8ebf/attachment-0001.html>