git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Re: Documentation: Clarify which paths git-clean will affect

From
NSNicolas Sebrecht <nicolas.s.dev@gmx.fr>
Date
May 5, 2009, 11:17 UTC
Message-ID
<20090505111707.GC1436@vidovic>
In-Reply-To
<20090505100506.GF27900@frsk.net>
The 05/05/09, Fredrik Skolmli wrote:
Show 15 quoted lines
> 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
Previous: Fredrik SkolmliNext: Thomas Rast
Message 4 of 9 in “Documentation: Clarify which paths git-clean will affect”
  1. Documentation: Clarify which paths git-clean will affectFredrik Skolmli, May 5, 2009
  2. Thomas RastMay 5, 2009
  3. Fredrik SkolmliMay 5, 2009
  4. Re: Documentation: Clarify which paths git-clean will affectNicolas Sebrecht, May 5, 2009
  5. Thomas RastMay 5, 2009
  6. Junio C HamanoMay 5, 2009
  7. Thomas RastMay 6, 2009
  8. Fredrik SkolmliMay 6, 2009
  9. Junio C HamanoMay 6, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.