From: Francis Daly <francis@daoine.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Some doc typo fixes
Date: Wed, 7 Jun 2006 18:46:14 +0100 [thread overview]
Message-ID: <20060607174614.GU29682@craic.sysops.org> (raw)
In-Reply-To: <7vwtbshp3d.fsf@assigned-by-dhcp.cox.net>
On Wed, Jun 07, 2006 at 10:07:02AM -0700, Junio C Hamano wrote:
> Junio C Hamano <junkio@cox.net> writes:
> > Francis Daly <francis@daoine.org> writes:
> > Thanks. I am not a native, and this is very much appreciated.
You're welcome.
> >> . It could be named hierarchically (i.e. separated with slash
> >> - `/`), but each of its component cannot begin with a dot `.`;
> >> + `/`), but each of its components cannot begin with a dot `.`;
> >
> > I am not sure; ...
>
> Sheesh, I was reading the diff backwards. Sorry.
No worries. I had a head-scratching moment, and suspect that the whole
stanza could be better phrased. If only there was someone who didn't
already know what it means, they could suggest which phrasing makes
it clear...
How about rewriting it as
It can include slash `/` for hierarchical (directory) grouping, but no
slash-separated component can begin with a dot `.`;
?
"can" instead of "could" fits the later parts, and it removes the
possessive and reverses the negative for something that (to my mind)
scans better.
Cheers,
f
--
Francis Daly francis@daoine.org
next prev parent reply other threads:[~2006-06-07 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 12:56 [PATCH] Some doc typo fixes Francis Daly
2006-06-07 16:48 ` Junio C Hamano
2006-06-07 17:07 ` Junio C Hamano
2006-06-07 17:46 ` Francis Daly [this message]
2006-06-08 7:22 ` Andreas Ericsson
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=20060607174614.GU29682@craic.sysops.org \
--to=francis@daoine.org \
--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).