Re: [PATCH v2] docs: rephrase and clarify the git status --short format

> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
> 
> > This uses text from Junio's email, so his sign-off will be required
> > here.  I assume that won't be a problem, but I can send a v3 if it is.
> 
> Actually I find the text so vastly improved from "here is my
> attempt" version in the discussion that, other than the paragraph
> structure, there is nothing left that I can call my contribution.
> I'll sign the resulting commit off anyway, though ;-)

> > +There are three different types of states that are shown using this format, and
> > +each one uses the `XY` syntax differently:
> > ...
> > +
> > +Note that the term _merge_ here also includes rebases using the default
> > +`--merge` strategy, cherry-picks, and anything else using the merge machinery.
> 
> Even if rebase uses the good-old "format-patch | am -3" pipeline, it
> would result in an index with entries at higher stages.  So I am not
> sure if this "Note that" helps the reader.

> > +In the following table, these three classes are shown in separate sections, and
> 
> This iteration has improved the "Three different classes of paths
> are shown" in the "here is my attempt" version to "Three different
> types of states ..."; shouldn't we be doing the same here with
> s/classes/types of states/?