Joe Hansche 5e57234ec6 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
2012-06-13 10:34:41 -07:00
2012-05-24 09:07:24 -07:00
2009-06-02 00:09:07 +02:00
2009-06-02 00:09:07 +02:00
2012-04-23 13:43:41 -07:00
2008-10-21 07:00:00 -07:00
2012-04-13 09:46:00 -07:00
2012-06-07 20:19:04 -07:00
2011-09-19 14:52:57 -07:00
2012-02-28 18:54:33 -08:00
Description
No description provided
Apache-2.0 35 MiB
Languages
Python 99.1%
Shell 0.9%