From: Jonathan Nieder <jrnieder@gmail.com>
To: John Keeping <john@keeping.me.uk>
Cc: git@vger.kernel.org, Martin von Zweigbergk <martinvonz@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] pull: use merge-base --fork-point when appropriate
Date: Mon, 9 Dec 2013 17:58:51 -0800 [thread overview]
Message-ID: <20131210015851.GA2311@google.com> (raw)
In-Reply-To: <b208a2edcaf47bf1a97ec19718854dc1b3646828.1386506845.git.john@keeping.me.uk>
John Keeping wrote:
> Since commit d96855f (merge-base: teach "--fork-point" mode, 2013-10-23)
> we can replace a shell loop in git-pull with a single call to
> git-merge-base. So let's do so.
>
> Signed-off-by: John Keeping <john@keeping.me.uk>
> ---
> git-pull.sh | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
Yay! Looks good.
prev parent reply other threads:[~2013-12-10 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 12:47 [PATCH] pull: use merge-base --fork-point when appropriate John Keeping
2013-12-10 1:58 ` Jonathan Nieder [this message]
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=20131210015851.GA2311@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=john@keeping.me.uk \
--cc=martinvonz@gmail.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).