Re: [PATCH] rebase docs: fix incorrect format of the section Behavioral Differences
- Date: Mon, 3 Dec 2018 21:56:19 +0100 (STD)
- From: Johannes Schindelin <Johannes.Schindelin@xxxxxx>
- Subject: Re: [PATCH] rebase docs: fix incorrect format of the section Behavioral Differences
On Mon, 3 Dec 2018, Johannes Sixt wrote:
> The text body of section Behavioral Differences is typeset as code,
> but should be regular text. Remove the indentation to achieve that.
> While here, prettify the language:
> - use "the x backend" instead of "x-based rebase";
> - use present tense instead of future tense;
> and use subsections instead of a list.
> Signed-off-by: Johannes Sixt <j6t@xxxxxxxx>
The changes look sensible to me.
> Cf. https://git-scm.com/docs/git-rebase#_behavioral_differences
> I actually did not test the result, because I don't have the
> The sentence "The am backend sometimes does not" is not very useful,
> but is not my fault ;) It would be great if it could be made more
> specific, but I do not know the details.
> Documentation/git-rebase.txt | 30 +++++++++++++++++-------------
> 1 file changed, 17 insertions(+), 13 deletions(-)
> diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
> index 80793bad8d..dff17b3178 100644
> --- a/Documentation/git-rebase.txt
> +++ b/Documentation/git-rebase.txt
> @@ -550,24 +550,28 @@ Other incompatible flag pairs:
> BEHAVIORAL DIFFERENCES
> - * empty commits:
> +There are some subtle differences how the backends behave.
> - am-based rebase will drop any "empty" commits, whether the
> - commit started empty (had no changes relative to its parent to
> - start with) or ended empty (all changes were already applied
> - upstream in other commits).
> +Empty commits
> +The am backend drops any "empty" commits, regardless of whether the
> +commit started empty (had no changes relative to its parent to
> +start with) or ended empty (all changes were already applied
> +upstream in other commits).
> - merge-based rebase does the same.
> +The merge backend does the same.
> - interactive-based rebase will by default drop commits that
> - started empty and halt if it hits a commit that ended up empty.
> - The `--keep-empty` option exists for interactive rebases to allow
> - it to keep commits that started empty.
> +The interactive backend drops commits by default that
> +started empty and halts if it hits a commit that ended up empty.
> +The `--keep-empty` option exists for the interactive backend to allow
> +it to keep commits that started empty.
> - * directory rename detection:
> +Directory rename detection
> - merge-based and interactive-based rebases work fine with
> - directory rename detection. am-based rebases sometimes do not.
> +The merge and interactive backends work fine with
> +directory rename detection. The am backend sometimes does not.