Re: What's cooking in git.git (Sep 2020, #03; Wed, 9)

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Sep 9, 2020, 23:07 UTC
Message-ID: <CAPig+cQnnukVoJTgsu1sGFWkAYv7V38-0s-CgYuMyizYHhSFQQ@mail.gmail.com>
In-Reply-To: <xmqq4ko6twc9.fsf@gitster.c.googlers.com>

On Wed, Sep 9, 2020 at 6:33 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 8 quoted lines

> * es/format-patch-interdiff-cleanup (2020-09-08) 3 commits
>  - format-patch: use 'origin' as start of current-series-range when known
>  - diff-lib: tighten show_interdiff()'s interface
>  - diff: move show_interdiff() from its own file to diff-lib
>
>  Code cleanup with a slight behaviour change when "format-patch
>  --range-diff=<prev> origin..HEAD" gives a single revision to
>  <prev>.

Perhaps this could be a bit more precise by saying something like:

    Code cleanup and make "format-patch --range-diff=<prev>
    <origin>..HEAD" not ignore <origin> when <prev> is a single
    revision.

Show 7 quoted lines

> * es/wt-add-detach (2020-09-06) 3 commits
>  - git-worktree.txt: discuss branch-based vs. throwaway worktrees
>  - worktree: teach `add` to recognize -d as shorthand for --detach
>  - git-checkout.txt: document -d short option for --detach
>
>  "git worktree add" learns the "--detach" option to create a new
>  worktree without being on a branch.

This needs a tweak to avoid being incorrect. "git worktree add" has understood --detach from the start. This series only teaches it -d as an alias for --detach. So, perhaps:

    "git worktree add" learns "-d" as short for "--detach".