From: Stepan Kasal <kasal@ucw.cz>
To: Jeff King <peff@peff.net>
Cc: John Keeping <john@keeping.me.uk>, git@vger.kernel.org
Subject: Re: Bug with git merge-base and a packed ref
Date: Wed, 12 Oct 2016 21:33:36 +0200 [thread overview]
Message-ID: <20161012193336.GA23072@ucw.cz> (raw)
In-Reply-To: <20161012163209.oadmm7xsmm7oeumr@sigill.intra.peff.net>
Hello,
On Wed, Oct 12, 2016 at 12:32:09PM -0400, Jeff King wrote:
> The --fork-point option looks in the reflog [...]
> On Wed, Oct 12, 2016 at 12:37:16PM +0200, Stepan Kasal wrote:
> > Could you please fix merge-base so that it understands packed refs?
I bet you nailed it; nothing with packed refs.
Thanks for correcting me.
Stepan
next prev parent reply other threads:[~2016-10-12 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 10:37 Bug with git merge-base and a packed ref Stepan Kasal
2016-10-12 16:32 ` Jeff King
2016-10-12 19:33 ` Stepan Kasal [this message]
2016-10-12 20:10 ` [PATCH] merge-base: handle --fork-point without reflog Jeff King
2016-10-12 21:29 ` Junio C Hamano
2016-10-13 6:34 ` Stepan Kasal
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=20161012193336.GA23072@ucw.cz \
--to=kasal@ucw.cz \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=peff@peff.net \
/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).