On 14 March 2011 23:26, Stavros Korokithakis <email address hidden> wrote:
> I'm too averse to committing half-working releases, I like to be able to restore to each commit and have things work reasonably well. I realise that this is a personal preference, and that I can commit and then uncommit, but these feel much less clean than the way bzr-pipeline does it (I believe
> git does it that way as well?)...
I believe git does also encourage you to commit before switching to
save half done work. I don't really like that either. At least an
option to save uncommitted work outside of the tree would be
worthwhile.
On 14 March 2011 23:26, Stavros Korokithakis <email address hidden> wrote:
> I'm too averse to committing half-working releases, I like to be able to restore to each commit and have things work reasonably well. I realise that this is a personal preference, and that I can commit and then uncommit, but these feel much less clean than the way bzr-pipeline does it (I believe
> git does it that way as well?)...
I believe git does also encourage you to commit before switching to
save half done work. I don't really like that either. At least an
option to save uncommitted work outside of the tree would be
worthwhile.