| commit | 9b3a448b4eee25050dc1e1c14c886e27e2985819 | |
| author | Pratik Karki <predatoramigo@gmail.com> | |
| Tue, 4 Sep 2018 22:00:05 +0000 (4 15:00 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 11 Oct 2018 05:12:45 +0000 (11 14:12 +0900) | ||
| tree | 391be8d9fbe458d45ede4f19f5df2742616ddbee | treesnapshot (tar.gz zip) |
| parent | 68e46d78683bf3cbf707fdad9d95f4cd72cc5dd5 | commitdiff |
builtin rebase: support `--allow-empty-message` option
This commit introduces the `--allow-empty-message` option to
`builtin/rebase.c`. The motivation behind this option is: if there are
empty messages (which is not allowed in Git by default, but can be
imported from different version control systems), the rebase will fail.
Using `--allow-empty-message` overrides that behaviour which will allow
the commits having empty messages to continue in rebase operation.
Note: a very recent change made this the default in the shell scripted
`git rebase`, therefore the builtin rebase does the same.
Signed-off-by: Pratik Karki <predatoramigo@gmail.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit introduces the `--allow-empty-message` option to
`builtin/rebase.c`. The motivation behind this option is: if there are
empty messages (which is not allowed in Git by default, but can be
imported from different version control systems), the rebase will fail.
Using `--allow-empty-message` overrides that behaviour which will allow
the commits having empty messages to continue in rebase operation.
Note: a very recent change made this the default in the shell scripted
`git rebase`, therefore the builtin rebase does the same.
Signed-off-by: Pratik Karki <predatoramigo@gmail.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin/rebase.c | diffblobblamehistory |