From: Junio C Hamano <gitster@pobox.com>
To: Alex Vandiver <alexmv@dropbox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Reporting index properties
Date: Fri, 06 Oct 2017 09:43:14 +0900 [thread overview]
Message-ID: <xmqqzi955cnx.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1710051625430.812@alexmv-linux> (Alex Vandiver's message of "Thu, 5 Oct 2017 16:39:20 -0700 (PDT)")
Alex Vandiver <alexmv@dropbox.com> writes:
> Do folks have feelings about surfacing this information, and where such
> logic should live?
Probably one of the t/helper/test-dump-*.c programs, if we already
do not have one.
next prev parent reply other threads:[~2017-10-06 0:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 23:39 [RFC] Reporting index properties Alex Vandiver
2017-10-06 0:43 ` Junio C Hamano [this message]
2017-10-06 0:47 ` Alex Vandiver
2017-10-06 2:39 ` Junio C Hamano
2017-10-06 19:26 ` Alex Vandiver
2017-10-06 3:13 ` Jonathan Nieder
2017-10-06 4:02 ` Junio C Hamano
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=xmqqzi955cnx.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=alexmv@dropbox.com \
--cc=git@vger.kernel.org \
/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.