git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2019, #02; Thu, 6)
Date: Wed, 12 Jun 2019 10:48:49 -0700	[thread overview]
Message-ID: <xmqq5zpak83i.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <a958e78b-523a-5578-24dc-77597a77c724@gmail.com> (Derrick Stolee's message of "Wed, 12 Jun 2019 09:19:34 -0400")

Derrick Stolee <stolee@gmail.com> writes:

>>  (this branch uses ds/commit-graph-write-refactor; is tangled with ds/close-object-store.)
>
> Sorry for the tangle here. I'll place the proper use of
> close_commit_graph(struct raw_object_store *) into my changes
> in the next version.

FWIW, "tangled" is no bad thing.  Two topics that build on the
mainline could be in one of these three kinds of relationship:

 - independent, sharing no commits, or
 - one builds on top of the entirety of the other, or
 - share some commits but neither is a subset of the other.

and "is tangled" was, even though I didn't really like it, the best
phrase I found to describe the third kind when I wrote the script
that manages the "What's cooking" report.

Thanks.

      reply	other threads:[~2019-06-12 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 19:57 What's cooking in git.git (Jun 2019, #02; Thu, 6) Junio C Hamano
2019-06-12  9:07 ` Duy Nguyen
2019-06-12 13:19 ` Derrick Stolee
2019-06-12 17:48   ` Junio C Hamano [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=xmqq5zpak83i.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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. 
Code repositories for project(s) associated with this public 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).