From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add revspec documentation for ':path', ':[0-3]:path' and git-describe
Date: Thu, 19 Oct 2006 11:57:02 +0700 [thread overview]
Message-ID: <fcaeb9bf0610182157i7cce5007r9552b2bf06988326@mail.gmail.com> (raw)
In-Reply-To: <7vlkncx6d2.fsf@assigned-by-dhcp.cox.net>
On 10/19/06, Junio C Hamano <junkio@cox.net> wrote:
> > As I'm not very good at English, please correct any mistake I made
>
> Thanks. I do not know about English, but I'd move things around
> to group them better. Most talk about committish but the
> colon-path are about trees and blobs.
It's ok to me.
--
Duy
prev parent reply other threads:[~2006-10-19 4:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 3:04 [PATCH] Add revspec documentation for ':path', ':[0-3]:path' and git-describe pclouds
2006-10-19 4:43 ` Junio C Hamano
2006-10-19 4:57 ` Nguyen Thai Ngoc Duy [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=fcaeb9bf0610182157i7cce5007r9552b2bf06988326@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).