Several ways to work with "uncomitted" state: 1. commit --amend and push --force to a working branch. The commits are overwritten each time and don't merge cleanly, but all intermediate versions are available in the reflog.
2. commit small things frequently in a topic branch, and later merge these commits into one when merging the feature. 3. use add --patch to commit the parts you know will stay, and don't let the uncomitted state grow too much. This is not SVN, there is no reason not to commit as frequently as possible. Committing often lets you have more choices later for merging, too. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
