git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Fredrik Skolmli <fredrik@frsk.net>
Cc: Thomas Rast <trast@student.ethz.ch>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH] Re: Documentation: Clarify which paths git-clean will affect
Date: Tue, 5 May 2009 13:17:07 +0200	[thread overview]
Message-ID: <20090505111707.GC1436@vidovic> (raw)
In-Reply-To: <20090505100506.GF27900@frsk.net>

The 05/05/09, Fredrik Skolmli wrote:
> On Tue, May 05, 2009 at 11:55:17AM +0200, Thomas Rast wrote:
> > Fredrik Skolmli wrote:
> > > --- a/Documentation/git-clean.txt
> > > +++ b/Documentation/git-clean.txt
> > > @@ -23,6 +23,9 @@ example, be useful to remove all build products.
> > >  If any optional `<path>...` arguments are given, only those paths
> > >  are affected.
> > >  
> > > +If no arguments are given, the cleaning is recursive, starting at the current
> > > +path.
> > 
> > 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?

Maybe:

If any optional `<path>...` arguments are given, only those paths are
affected. If no arguments are given, the cleaning starts at the current
path.

The cleaning are recursive.

-- 
Nicolas Sebrecht

  reply	other threads:[~2009-05-05 11:17 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     ` Nicolas Sebrecht [this message]
2009-05-05 12:26     ` Thomas Rast
2009-05-05 16:20       ` 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=20090505111707.GC1436@vidovic \
    --to=nicolas.s.dev@gmx.fr \
    --cc=fredrik@frsk.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=trast@student.ethz.ch \
    /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).