Re: odd behavior with git-rebase
- From
Jay Soffian <jaysoffian@gmail.com>
- Date
- Mar 27, 2012, 01:58 UTC
- Message-ID
- <CAG+J_Dx8o_cpS3zLyRf66dgsRZEzP-yD8nBwLmfZhWkydX_MVA@mail.gmail.com>
- In-Reply-To
- <CABURp0oJwM-KtdBRVHgvOaqFVjA-MEAfJoJH=52Y=QRcgFL+3Q@mail.gmail.com>
On Mon, Mar 26, 2012 at 2:29 PM, Phil Hord <phil.hord@gmail.com> wrote:
Show 5 quoted lines
> Can we have three behaviors? > > A: Current mode, stop and error on empty commits > B: --keep-empty, to retain empty commits without further notice > C: --purge-empty, to remove empty commits without further notice
FWIW, filter-branch uses "--prune-empty", should we wish to be consistent.
j.