tree 40f4eab3f13e5b4a1ca4ff3f501539ae63f44229
parent 5d016502ebc68bc054d85c98c6cdb51e0b63a1f5
author Joe Hansche <jhansche@myyearbook.com> 1330965679 -0500
committer Shawn O. Pearce <sop@google.com> 1339608881 -0700

Support automatically stashing local modifications during repo-rebase.

Currently repo-rebase requires that all modifications be committed
locally before it will allow the rebase. In high-velocity environments,
you may want to just pull in newer code without explicitly creating
local commits, which is typically achieved using git-stash.

If called with the --auto-stash command line argument, and it is
determined that the current index is dirty, the local modifications
are stashed, and the rebase continues.  If a stash was performed, that
stash is popped once the rebase completes.

Note that there is still a possibility that the git-stash pop will
result in a merge conflict.

Change-Id: Ibe3da96f0b4486cb7ce8d040639187e26501f6af