From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Derrick Stolee <stolee@gmail.com>,
Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, avarab@gmail.com, garimasigit@gmail.com,
Derrick Stolee <dstolee@microsoft.com>
Subject: Re: [PATCH 1/1] fetch: add fetch.writeCommitGraph config setting
Date: Fri, 06 Sep 2019 13:42:55 -0700 [thread overview]
Message-ID: <xmqqpnkdma0g.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190906191622.GA7096@sigill.intra.peff.net> (Jeff King's message of "Fri, 6 Sep 2019 15:16:22 -0400")
Jeff King <peff@peff.net> writes:
> I suppose so. But I think the "stock git without any other job
> infrastructure" case would still benefit.
Oh, no question about it.
I did question if an automatic writing would benefit the side that
receives a push when you brought up the usual "fetch.* and receive.*
for separate configuration, transfer.* when want to rule them both"
convention, which is a good idea if only for consistency, but the
question was if it helps the receiving end of a push to the same
degree as it would help the repository that fetches.
next prev parent reply other threads:[~2019-09-06 20:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 2:22 [PATCH 0/1] Write commit-graph on fetch Derrick Stolee via GitGitGadget
2019-09-03 2:22 ` [PATCH 1/1] fetch: add fetch.writeCommitGraph config setting Derrick Stolee via GitGitGadget
2019-09-03 19:05 ` Junio C Hamano
2019-09-03 23:36 ` Derrick Stolee
2019-09-06 21:46 ` Junio C Hamano
2019-09-07 4:51 ` Jeff King
2019-09-09 17:53 ` Junio C Hamano
2019-09-04 3:08 ` Jeff King
2019-09-05 20:37 ` Junio C Hamano
2019-09-06 17:00 ` Derrick Stolee
2019-09-06 17:56 ` Jeff King
2019-09-06 18:24 ` Junio C Hamano
2019-09-06 19:16 ` Jeff King
2019-09-06 20:42 ` Junio C Hamano [this message]
2019-09-06 21:04 ` Derrick Stolee
2019-09-06 21:57 ` Junio C Hamano
2019-09-07 4:47 ` Jeff King
2019-09-07 4:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqpnkdma0g.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=dstolee@microsoft.com \
--cc=garimasigit@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=peff@peff.net \
--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.
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 NNTP newsgroup(s).