git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)
Date: Mon, 17 Sep 2018 14:35:49 -0400	[thread overview]
Message-ID: <43e8d5aa-5418-2e2d-2097-9e21e7a74825@gmail.com> (raw)
In-Reply-To: <xmqqy3c3agkr.fsf@gitster-ct.c.googlers.com>

On 9/14/2018 5:56 PM, Junio C Hamano wrote:
> * ds/format-commit-graph-docs (2018-08-21) 2 commits
>   - commit-graph.txt: improve formatting for asciidoc
>   - Docs: Add commit-graph tech docs to Makefile
>
>   Design docs for the commit-graph machinery is now made into HTML as
>   well as text.
>
>   Will discard.
>   I am inclined to drop these, as I do not see much clarity in HTML
>   output over the text source.  Opinions?

Discarding is fine. I originally created it because I thought we were 
supposed to mark all documents for HTML generation. You're right, the 
HTML doesn't add anything.

> * ds/commit-graph-with-grafts (2018-08-21) 8 commits
>   - commit-graph: close_commit_graph before shallow walk
>   - commit-graph: not compatible with uninitialized repo
>   - commit-graph: not compatible with grafts
>   - commit-graph: not compatible with replace objects
>   - test-repository: properly init repo
>   - commit-graph: update design document
>   - refs.c: upgrade for_each_replace_ref to be a each_repo_ref_fn callback
>   - refs.c: migrate internal ref iteration to pass thru repository argument
>
>   The recently introduced commit-graph auxiliary data is incompatible
>   with mechanisms such as replace & grafts that "breaks" immutable
>   nature of the object reference relationship.  Disable optimizations
>   based on its use (and updating existing commit-graph) when these
>   incompatible features are in use in the repository.
>
>   Replaced with a newer version.

I think this has been the same note for a few weeks now. What does it 
mean? Did I send a new version out that you haven't picked up?

Also, my "git log --topo-order" series was never picked up, but I see it 
has conflicts with 'next' now, so I'll rebase to resolve conflicts and 
send a v2.

Thanks,
-Stolee


  parent reply	other threads:[~2018-09-17 18:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14 21:56 What's cooking in git.git (Sep 2018, #03; Fri, 14) Junio C Hamano
2018-09-15 20:17 ` Antonio Ospite
2018-09-17 15:11   ` Junio C Hamano
2018-09-16  6:39 ` Duy Nguyen
2018-09-16 15:09   ` Ævar Arnfjörð Bjarmason
2018-09-17  2:39   ` Jeff King
2018-09-17 17:51     ` Junio C Hamano
2018-09-17 18:22       ` Jeff King
2018-09-17 18:26         ` Jonathan Nieder
2018-09-16 12:01 ` brian m. carlson
2018-09-17 15:10   ` Junio C Hamano
2018-09-17 18:35 ` Derrick Stolee [this message]
2018-09-17 19:04   ` Junio C Hamano
2018-09-17 22:54 ` Junio C Hamano
2018-09-19  3:49 ` [PATCH] pack-objects: handle island check for "external" delta base Jeff King
2018-09-19 18:34   ` Martin Ågren
2018-09-19 18:43     ` Jeff King

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=43e8d5aa-5418-2e2d-2097-9e21e7a74825@gmail.com \
    --to=stolee@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).