archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <>
To: "Johannes Schindelin via GitGitGadget" <>
Cc:, Johannes Schindelin <>
Subject: Re: [PATCH 1/1] pull --rebase=<type>: allow single-letter abbreviations for the type
Date: Mon, 06 Aug 2018 12:59:54 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Johannes Schindelin via GitGitGadget's message of "Sat, 04 Aug 2018 12:23:09 -0700 (PDT)")

"Johannes Schindelin via GitGitGadget" <>

> From: Johannes Schindelin <>
> Git for Windows' original 4aa8b8c8283 (Teach 'git pull' to handle
> --rebase=interactive, 2011-10-21) had support for the very convenient
> abbreviation
> 	git pull --rebase=i
> which was later lost when it was ported to the builtin `git pull`, and
> it was not introduced before the patch eventually made it into Git as
> f5eb87b98dd (pull: allow interactive rebase with --rebase=interactive,
> 2016-01-13).
> However, it is *really* a useful short hand for the occasional rebasing
> pull on branches that do not usually want to be rebased.
> So let's reintroduce this convenience, at long last.
> Signed-off-by: Johannes Schindelin <>
> ---

Makes sense, whether this patch is adding back what in the past
existed only in the Windows port but lost, and whether the lossage
was long time ago or in just a few releases go, or it is adding a
complete new feature for that matter.  This looks like a good

Will queue.

  reply	other threads:[~2018-08-06 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-04 19:23 [PATCH 0/1] Support git pull --rebase=i <remote> <branch> Johannes Schindelin via GitGitGadget
2018-08-04 19:23 ` [PATCH 1/1] pull --rebase=<type>: allow single-letter abbreviations for the type Johannes Schindelin via GitGitGadget
2018-08-06 19:59   ` Junio C Hamano [this message]
2018-08-07 12:02     ` Johannes Schindelin
2018-08-07 19:28   ` Ævar Arnfjörð Bjarmason
2018-08-08 19:51     ` Junio C Hamano
2018-08-08 22:19       ` 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:

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

  git send-email \ \ \ \ \ \

* 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).