From: Clemens Buchacher <drizzd@aon.at>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Jeff King <peff@peff.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Missing capabilities in Documentation/technical/protocol-capbilities.txt
Date: Wed, 17 Jul 2013 13:31:40 +0200 [thread overview]
Message-ID: <20130717113140.GA22252@ecki.lan> (raw)
In-Reply-To: <CACsJy8BcEfc33HNxQB+_msbkbcxFfqg1xOpeRxNGL_cUqruE0w@mail.gmail.com>
On Mon, Jul 15, 2013 at 07:25:19PM +0700, Duy Nguyen wrote:
>
> I noticed that "quiet" and "agent" capabilities were missing in
> protocol-capabilitities.txt. I have a rough idea what they do, but I
> think it's best to be documented by the authors. Maybe you have some
> time to make a patch?
Hi Duy,
I am sorry to disappoint, but if I had time to work on Git, I'd rather
be writing code. I have some great ideas if you are interested. :-P
Besides, I barely even remember that it was me who implemented the
"quiet" capability. In order to write documentation for it, I would have
to research the implementation as much as anyone.
Cheers,
Clemens
next prev parent reply other threads:[~2013-07-17 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 12:25 Missing capabilities in Documentation/technical/protocol-capbilities.txt Duy Nguyen
2013-07-17 11:31 ` Clemens Buchacher [this message]
2013-07-24 8:00 ` [PATCH 0/4] protocol-capabilities documentation updates Jeff King
2013-07-24 8:01 ` [PATCH 1/4] docs: fix 'report-status' protocol capability thinko Jeff King
2013-07-24 8:01 ` [PATCH 2/4] docs: note that receive-pack knows side-band-64k capability Jeff King
2013-07-24 8:03 ` [PATCH 3/4] document 'agent' protocol capability Jeff King
2013-07-24 8:03 ` [PATCH 4/4] document 'quiet' receive-pack capability Jeff King
2013-07-26 11:01 ` [PATCH 5/4] document 'allow-tip-sha1-in-want' capability Nguyễn Thái Ngọc Duy
2013-07-26 15:36 ` 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=20130717113140.GA22252@ecki.lan \
--to=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--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).