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, Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: ds/multi-pack-index (was Re: What's cooking in git.git (Jul 2018, #03; Wed, 25))
Date: Wed, 01 Aug 2018 15:13:33 -0700	[thread overview]
Message-ID: <xmqqo9el68he.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <f17a6d57-e6cb-9efa-d648-cd4f298dc47f@gmail.com> (Derrick Stolee's message of "Wed, 1 Aug 2018 16:53:01 -0400")

Derrick Stolee <stolee@gmail.com> writes:

> On 7/25/2018 6:13 PM, Junio C Hamano wrote:
>> * ds/multi-pack-index (2018-07-20) 23 commits
>> ...
>>   Ready to move to 'next', with some known issues to be followed up?
>>   cf. <xmqqefg8uplg.fsf@gitster-ct.c.googlers.com>
> I'm not sure if there is anything actionable for me to do in response
> to this message.

As I said elsewhere, "cf. <msg>" list does not attempt to be a
complete enumeration of things to be fixed.  It is a (sub)set of
pointers into list archive to help me in integration cycles to
decide if I can comfortably merge each topic to 'next' (or update
"What's cooking" to mark the topic as "Will merge").  FWIW, that
particular message is not even an objection ;-) It was telling the
future-me "hey, I looked at this series and found nothing wrong in
it, so no need to read them again to refresh your memory".

The other one is a good reminder, again, given primarily to
future-me, that the topic is known to be imperfect and the
discussion seemed to favor moving "with some known issues to be
followed up", so I should not waste time re-reading and poke the
same holes.


      reply	other threads:[~2018-08-01 22:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 22:13 What's cooking in git.git (Jul 2018, #03; Wed, 25) Junio C Hamano
2018-07-25 22:56 ` Stefan Beller
2018-07-25 23:43   ` Junio C Hamano
2018-07-26  4:14     ` Junio C Hamano
2018-07-26 16:56     ` Junio C Hamano
2018-07-25 23:47   ` Junio C Hamano
2018-07-25 23:48   ` Junio C Hamano
2018-07-26  4:15     ` Junio C Hamano
2018-07-26  6:07 ` Оля Тележная
2018-07-26 16:57   ` Junio C Hamano
2018-08-02 12:41     ` Christian Couder
2018-08-02 18:40       ` Junio C Hamano
2018-07-26  7:24 ` Jeff King
2018-07-26 16:57   ` Junio C Hamano
2018-07-26 20:46     ` Jeff King
2018-07-27 14:28 ` Ævar Arnfjörð Bjarmason
2018-07-27 17:28   ` Junio C Hamano
2018-07-30 13:16     ` range-diff, was " Johannes Schindelin
2018-07-30 15:41       ` Junio C Hamano
2018-08-01 16:01         ` Johannes Schindelin
2018-08-01 19:11           ` Junio C Hamano
2018-08-01 20:44 ` ds/reachable (was Re: What's cooking in git.git (Jul 2018, #03; Wed, 25)) Derrick Stolee
2018-08-01 21:55   ` Junio C Hamano
2018-08-01 20:53 ` ds/multi-pack-index " Derrick Stolee
2018-08-01 22:13   ` 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=xmqqo9el68he.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=stolee@gmail.com \
    --cc=sunshine@sunshineco.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).