From: Jeff King <email@example.com> To: Johannes Schindelin <Johannes.Schindelin@gmx.de> Cc: Jeff Hostetler <firstname.lastname@example.org>, Ben Peart <email@example.com>, firstname.lastname@example.org, email@example.com, Jeff Hostetler <firstname.lastname@example.org> Subject: Re: [PATCH v4 0/4] Add --no-ahead-behind to status Date: Wed, 10 Jan 2018 02:41:59 -0500 [thread overview] Message-ID: <20180110074159.GA16315@sigill.intra.peff.net> (raw) In-Reply-To: <nycvar.QRO.220.127.116.111091407480.37@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz> On Tue, Jan 09, 2018 at 02:15:47PM +0100, Johannes Schindelin wrote: > > I like this direction a lot. I had hoped we could say "100+ commits > > ahead", > > How about "100+ commits apart" instead? Yeah, that is probably more accurate for the general case. > > but I don't think we can do so accurately without generation numbers. > > Even with generation numbers, it is not possible to say whether two given > commits reflect diverging branches or have an ancestor-descendant > relationship (or in graph speak: whether they are comparable). > > It could potentially make it possible to cut off the commit traversal, but > I do not even see how that would be possible. > > The only thing you could say for sure is that two different commits with > the same generation number are for sure "uncomparable", i.e. reflect > diverging branches. I think sometimes we can say more. E.g., imagine we have two commits, A and B, with generation numbers N and N+1000. We walk back 100 commits deep from B and end up at a commit around N+900. We know that there are at least 100 commits in B that are not in A (the 100 we walked, which we know cannot be ancestors of A because of their generation numbers). That's true even if there is no ancestry relationship between the two commits at all. But we cannot say in that case how many (if any) commits are in A but not B. So we can say "100+ commits ahead, unknown behind" (or if the two generation numbers are reversed, we can say "unknown ahead, 100+ commits behind). In the more general case, we could actually walk _past_ generation N, and end up at N-25 or similar. There we can't say anything intelligent about the commits with generations <= N. But we could say something like "there are 75 commits in B that cannot be in A" (note that it's probably _not_ actually 75; it's however many we walked until we crossed N). So that was what I was getting at in the earlier mail. We can sometimes give a partial answer. But I think giving that partial answer is likely to be more confusing than useful to a user, because there are a lot of caveats about how much we know for a given situation. And I think from what you wrote below that you probably agree with that (that we can make a few claims, but not enough to really be useful). -Peff
prev parent reply other threads:[~2018-01-10 7:42 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-08 15:48 Jeff Hostetler 2018-01-08 15:48 ` [PATCH v4 1/4] stat_tracking_info: return +1 when branches not equal Jeff Hostetler 2018-01-08 15:48 ` [PATCH v4 2/4] status: add --[no-]ahead-behind to status and commit for V2 format Jeff Hostetler 2018-01-08 15:48 ` [PATCH v4 3/4] status: update short status to respect --no-ahead-behind Jeff Hostetler 2018-01-08 15:48 ` [PATCH v4 4/4] status: support --no-ahead-behind in long format Jeff Hostetler 2018-01-08 19:49 ` [PATCH v4 0/4] Add --no-ahead-behind to status Ben Peart 2018-01-08 20:04 ` Jeff Hostetler 2018-01-09 7:20 ` Jeff King 2018-01-09 13:15 ` Johannes Schindelin 2018-01-09 14:29 ` Derrick Stolee 2018-01-09 14:56 ` Jeff Hostetler 2018-01-09 16:48 ` Johannes Schindelin 2018-01-10 7:47 ` Jeff King 2018-01-10 20:22 ` Junio C Hamano 2018-01-11 9:39 ` Jeff King 2018-01-10 7:41 ` Jeff King [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 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=20180110074159.GA16315@sigill.intra.peff.net \ --email@example.com \ --cc=Johannes.Schindelin@gmx.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v4 0/4] Add --no-ahead-behind to status' \ /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
Code repositories for project(s) associated with this 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).