From: Thomas Rast <trast@student.ethz.ch>
To: Fredrik Skolmli <fredrik@frsk.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: [PATCH] Documentation: Clarify which paths git-clean will affect
Date: Tue, 5 May 2009 14:26:14 +0200 [thread overview]
Message-ID: <200905051426.18814.trast@student.ethz.ch> (raw)
In-Reply-To: <20090505100506.GF27900@frsk.net>
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
Fredrik Skolmli wrote:
> On Tue, May 05, 2009 at 11:55:17AM +0200, Thomas Rast wrote:
> > That makes it sound as if the <path> case was not recursive, but it
> > is!
>
> Auch, good point. Any suggestions on how to formulate it?
I'm not entirely happy with it, but if we're going to change it, I'd
put the "recursive" near the top to make it more visible. Maybe like
so:
-- 8< --
diff --git i/Documentation/git-clean.txt w/Documentation/git-clean.txt
index 43b2de7..3550fc0 100644
--- i/Documentation/git-clean.txt
+++ w/Documentation/git-clean.txt
@@ -13,15 +13,15 @@ SYNOPSIS
DESCRIPTION
-----------
-This allows cleaning the working tree by removing files that are not
+Cleans the working tree by recursively removing files that are not
under version control.
Normally, only files unknown to git are removed, but if the '-x'
option is specified, ignored files are also removed. This can, for
example, be useful to remove all build products.
-If any optional `<path>...` arguments are given, only those paths
-are affected.
+If any optional `<path>...` arguments are given, those paths are
+affected. Otherwise, the cleaning starts at the current directory.
OPTIONS
-------
-- >8 --
As a side note, a random survey among a few other manpages did not
give any conclusive advice on the formulation of the first sentence.
I originally wanted to make it imperative ("clean the working
tree..."), but my perception may be skewed by the commit message
guidelines.
--
Thomas Rast
trast@{inf,student}.ethz.ch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-05-05 12:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 9:13 [PATCH] Documentation: Clarify which paths git-clean will affect Fredrik Skolmli
2009-05-05 9:55 ` Thomas Rast
2009-05-05 10:05 ` Fredrik Skolmli
2009-05-05 11:17 ` [PATCH] " Nicolas Sebrecht
2009-05-05 12:26 ` Thomas Rast [this message]
2009-05-05 16:20 ` [PATCH] " Junio C Hamano
2009-05-06 13:24 ` Thomas Rast
2009-05-06 16:31 ` Fredrik Skolmli
2009-05-06 17:57 ` 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=200905051426.18814.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=fredrik@frsk.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nicolas.s.dev@gmx.fr \
/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).