From: "Kaartic.Sivaraam" <kaartic.sivaraam@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: protocol v2: More data transmitted between client and server since v2.20.0
Date: Sat, 2 Feb 2019 23:31:26 +0530 [thread overview]
Message-ID: <0da174c7-40cd-c245-abbf-6aa7a657f5a3@gmail.com> (raw)
In-Reply-To: <20190128212305.GA23587@sigill.intra.peff.net>
Hi Peff,
Thanks for sharing the details about that spooky behaviour! Also, thanks
for suggesting an alternative way to show the advantage of using
protocol v2. I'll refer your post in that blog's comment to let them know.
Thanks,
Sivaraam
next prev parent reply other threads:[~2019-02-02 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 6:15 protocol v2: More data transmitted between client and server since v2.20.0 Kaartic Sivaraam
2019-01-28 21:23 ` Jeff King
2019-02-02 18:01 ` Kaartic.Sivaraam [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-20 21:30 Kaartic Sivaraam
2019-01-20 21:35 ` Kaartic Sivaraam
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=0da174c7-40cd-c245-abbf-6aa7a657f5a3@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).