From: Jacob Keller <jacob.keller@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Derrick Stolee <stolee@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Jakub Narebski <jnareb@gmail.com>,
Jeff Hostetler <git@jeffhostetler.com>
Subject: Re: commit-graph: change in "best" merge-base when ambiguous
Date: Mon, 21 May 2018 15:25:40 -0700 [thread overview]
Message-ID: <CA+P7+xpC6bSy0wJhmgT=UMev2AdDz0LVG11Ok7Y5j0Fsr-s08Q@mail.gmail.com> (raw)
In-Reply-To: <20180521215443.GC16623@sigill.intra.peff.net>
On Mon, May 21, 2018 at 2:54 PM, Jeff King <peff@peff.net> wrote:
> Yes, I think this is clearly a case where all of the single merge-bases
> we could show are equally good. And I don't think we should promise to
> show a particular one, but I _do_ think it's friendly for us to have
> deterministic tie-breakers (we certainly don't now).
>
> -Peff
Right. I think we should probably have some mechanism that will allow
us to always give the same answer, even if it's somewhat arbitrary.
Regards,
Jake
next prev parent reply other threads:[~2018-05-21 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 18:10 commit-graph: change in "best" merge-base when ambiguous Derrick Stolee
2018-05-21 18:33 ` Elijah Newren
2018-05-21 21:50 ` Jeff King
2018-05-21 22:28 ` Stefan Beller
2018-05-21 21:54 ` Jeff King
2018-05-21 22:25 ` Jacob Keller [this message]
2018-05-22 5:39 ` Michael Haggerty
2018-05-22 12:48 ` Derrick Stolee
2018-05-24 22:08 ` Jakub Narebski
2018-05-25 6:03 ` Michael Haggerty
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='CA+P7+xpC6bSy0wJhmgT=UMev2AdDz0LVG11Ok7Y5j0Fsr-s08Q@mail.gmail.com' \
--to=jacob.keller@gmail.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
--cc=stolee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.