From: Jakub Narebski <jnareb@gmail.com>
To: Guanqun Lu <guanqun.lu@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] fix typo in Documentation
Date: Wed, 04 Feb 2009 01:26:09 -0800 (PST) [thread overview]
Message-ID: <m38womwo2b.fsf@localhost.localdomain> (raw)
In-Reply-To: <1233781241-721-1-git-send-email-guanqun.lu@gmail.com>
Guanqun Lu <guanqun.lu@gmail.com> writes:
> Signed-off-by: Guanqun Lu <guanqun.lu@gmail.com>
> ---
> Documentation/technical/api-strbuf.txt | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Minor nit: I would add _where_ did you fix typy, i.e. instead of just
fix typo in Documentation
I'd use
fix typo in strbuf API documentation
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-02-04 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 21:00 [PATCH 1/2] fix typo in Documentation Guanqun Lu
2009-02-04 5:30 ` Sverre Rabbelier
2009-02-04 9:26 ` Jakub Narebski [this message]
2009-02-05 6:27 ` Guanqun Lu
2009-02-04 21:00 ` [PATCH 2/2] add test-dump-cache-tree in Makefile Guanqun Lu
2009-02-04 7:46 ` Junio C Hamano
2009-02-04 9:31 ` Jakub Narebski
2009-02-06 13:43 ` [PATCH 1/2] fix typo in Documentation Mikael Magnusson
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=m38womwo2b.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=guanqun.lu@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).