On Mon, Aug 06, 2012 at 12:00:16PM +0100, Chris Webb wrote:
> Neil Horman writes:
>
> > Having read over this thread, I think this is definately the way to go. As
> > discussed having cherry-pick stop and give the user a chance to fix empty
> > history messages by default, and providing a switch
Neil Horman writes:
> Having read over this thread, I think this is definately the way to go. As
> discussed having cherry-pick stop and give the user a chance to fix empty
> history messages by default, and providing a switch to override that behavior
> makes sense to me. That said, shouldn't
On Thu, Aug 02, 2012 at 11:38:51AM +0100, Chris Webb wrote:
> Scripts such as git rebase -i cannot currently cherry-pick commits which
> have an empty commit message, as git cherry-pick calls git commit
> without the --allow-empty-message option.
>
> Add an --allow-empty-message option to git cher
Scripts such as git rebase -i cannot currently cherry-pick commits which
have an empty commit message, as git cherry-pick calls git commit
without the --allow-empty-message option.
Add an --allow-empty-message option to git cherry-pick which is passed
through to git commit, so this behaviour can b
4 matches
Mail list logo
