Re: [PATCH 7/8] Documentation/cherry-pick: describe passing more than one commit

From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: Jun 1, 2010, 09:29 UTC
Message-ID: <AANLkTikHODw5irE-84bkztWhUKgP8v1PG9zTW1Ea6WRs@mail.gmail.com>
In-Reply-To: <20100531194240.28729.50475.chriscool@tuxfamily.org>

Hi,

Christian Couder <chriscool@tuxfamily.org> wrote:

Show 16 quoted lines

>  -n::
>  --no-commit::
> -       Usually the command automatically creates a commit.
> -       This flag applies the change necessary to cherry-pick
> -       the named commit to your working tree and the index,
> -       but does not make the commit.  In addition, when this
> -       option is used, your index does not have to match the
> -       HEAD commit.  The cherry-pick is done against the
> -       beginning state of your index.
> +       Usually the command automatically creates some commits.  This
> +       flag applies the change necessary to cherry-pick the named
> +       commits to your working tree and the index, but does not make
> +       the commits.  In addition, when this option is used, your
> +       index does not have to match the HEAD commit.  The cherry-pick
> +       is done against the beginning state of your index.
>  +

Avoid re-wrapping the text so it's easy to see the changes that you have introduced in subsequent blames- you've just changed the word "commit" to "commits".

> +Examples
> +--------

Style nitpick: shouldn't the word "Examples" be in all-caps?

-- Ram