git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH/RFC] range-diff: make output format more useful for "rebase --onto"
Date: Fri, 17 Sep 2021 20:06:00 -0400	[thread overview]
Message-ID: <CAPig+cSJ4tsJFPK2UQsj_m6DxQteLXjYSzVcrP=Wyeox5mJu7Q@mail.gmail.com> (raw)
In-Reply-To: <xmqqv92yg5y6.fsf@gitster.g>

On Fri, Sep 17, 2021 at 7:04 PM Junio C Hamano <gitster@pobox.com> wrote:
> In a range-diff output, we often see an early part of an updated
> series having no changes since the previous iteration.  After
> applying an updated patch submission to the same base as the
> previous round,
> [...]
> Now, after noticing that up to step #5 there is no change since the
> previous round, cleaning up the application result with
>
>     $ git rebase --onto 097b89c815 97b89c8150
>
> will help making it easier to see that earliser part did not change
> before committing this in the longer term history.

s/earliser/earlier/

  reply	other threads:[~2021-09-18  0:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 23:04 [PATCH/RFC] range-diff: make output format more useful for "rebase --onto" Junio C Hamano
2021-09-18  0:06 ` Eric Sunshine [this message]
2021-09-18  3:29 ` Taylor Blau
2021-09-18  7:29 ` Ævar Arnfjörð Bjarmason
2021-09-19  7:34   ` Ævar Arnfjörð Bjarmason
2021-09-19 21:22   ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='CAPig+cSJ4tsJFPK2UQsj_m6DxQteLXjYSzVcrP=Wyeox5mJu7Q@mail.gmail.com' \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).