git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Sep 2020, #03; Wed, 9)
Date: Wed, 09 Sep 2020 21:52:38 -0700	[thread overview]
Message-ID: <xmqqimcms06h.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAPig+cQnnukVoJTgsu1sGFWkAYv7V38-0s-CgYuMyizYHhSFQQ@mail.gmail.com> (Eric Sunshine's message of "Wed, 9 Sep 2020 19:07:22 -0400")

Eric Sunshine <sunshine@sunshineco.com> writes:

> On Wed, Sep 9, 2020 at 6:33 PM Junio C Hamano <gitster@pobox.com> wrote:
>> * 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.

Sure.  I didn't realize we can be more specific without spending too
many more bytes.  Let me steal that description.

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

Thanks.

  reply	other threads:[~2020-09-10  4:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 22:32 What's cooking in git.git (Sep 2020, #03; Wed, 9) Junio C Hamano
2020-09-09 23:07 ` Eric Sunshine
2020-09-10  4:52   ` Junio C Hamano [this message]
2020-09-15 22:48     ` Eric Sunshine
2020-09-15 22:54       ` Junio C Hamano
2020-09-15 19:05 ` Jakub Narębski
2020-09-15 19:32   ` Taylor Blau
2020-09-15 21:14   ` Junio C Hamano
2020-09-15 21:25     ` Jakub Narębski
2020-09-15 21:45       ` Junio C Hamano
2020-09-15 21:48         ` Taylor Blau
2020-09-15 22:32           ` Junio C Hamano
2020-09-15 22:02         ` Jakub Narębski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqimcms06h.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sunshine@sunshineco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).