From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Git Mailing List <git@vger.kernel.org>,
Michael J Gruber <git@drmicha.warpmail.net>,
Sverre Rabbelier <srabbelier@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v4] Improve remote-helpers documentation
Date: Mon, 22 Mar 2010 22:27:06 +0530 [thread overview]
Message-ID: <f3271551003220957q5db34547t69b425f708628dff@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1003221143250.14365@iabervon.org>
> But I'm fine with whichever format is most helpful for someone trying to
> read the document (that is, to you).
Your format is indeed more elegant- I've incorporated this change in v5. Thanks.
-- Ram
prev parent reply other threads:[~2010-03-22 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 13:04 [PATCH v4] Improve remote-helpers documentation Ramkumar Ramachandra
2010-03-22 16:32 ` Daniel Barkalow
2010-03-22 16:57 ` Ramkumar Ramachandra [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f3271551003220957q5db34547t69b425f708628dff@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=srabbelier@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).