{"thread":{"id":"19184","subject":"[PATCH] Documentation: Clarify which paths git-clean will affect","startedAt":"2009-05-05T09:13:03Z","lastAt":"2009-05-06T17:57:54Z","messageCount":9,"participants":["Fredrik Skolmli","Thomas Rast","Nicolas Sebrecht","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"113027","messageId":"20090505091302.GB27900@frsk.net","threadId":"19184","inReplyTo":null,"subject":"[PATCH] Documentation: Clarify which paths git-clean will affect","fromName":"Fredrik Skolmli","fromEmail":"fredrik@frsk.net","sentAt":"2009-05-05T09:13:03Z","receivedAt":"2009-05-05T09:13:03Z","isPatch":true,"sender":{"key":"fredrik@frsk.net","avatar":"https://avatars.githubusercontent.com/u/40261?v=4"},"body":"\nSigned-off-by: Fredrik Skolmli \n---\n Documentation/git-clean.txt | 3 +++\n 1 files changed, 3 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-clean.txt b/Documentation/git-clean.txt\nindex 43b2de7..ec6f743 100644\n--- a/Documentation/git-clean.txt\n+++ b/Documentation/git-clean.txt\n@@ -23,6 +23,9 @@ example, be useful to remove all build products.\n If any optional `...` arguments are given, only those paths\n are affected.\n \n+If no arguments are given, the cleaning is recursive, starting at the current\n+path.\n+\n OPTIONS\n -------\n -d::\n-- \n1.6.3.rc4.106.g0303f\n\n-- \nFredrik Skolmli\n"},{"id":"113029","messageId":"200905051155.28985.trast@student.ethz.ch","threadId":"19184","inReplyTo":"20090505091302.GB27900@frsk.net","subject":"Re: [PATCH] Documentation: Clarify which paths git-clean will affect","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2009-05-05T09:55:17Z","receivedAt":"2009-05-05T09:55:17Z","isPatch":true,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Fredrik Skolmli wrote:\n> --- a/Documentation/git-clean.txt\n> +++ b/Documentation/git-clean.txt\n> @@ -23,6 +23,9 @@ example, be useful to remove all build products.\n> If any optional `...` arguments are given, only those paths\n> are affected.\n> \n> +If no arguments are given, the cleaning is recursive, starting at the current\n> +path.\n\nThat makes it sound as if the case was not recursive, but it\nis!\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"113028","messageId":"20090505100506.GF27900@frsk.net","threadId":"19184","inReplyTo":"200905051155.28985.trast@student.ethz.ch","subject":"Re: [PATCH] Documentation: Clarify which paths git-clean will affect","fromName":"Fredrik Skolmli","fromEmail":"fredrik@frsk.net","sentAt":"2009-05-05T10:05:07Z","receivedAt":"2009-05-05T10:05:07Z","isPatch":true,"sender":{"key":"fredrik@frsk.net","avatar":"https://avatars.githubusercontent.com/u/40261?v=4"},"body":"On Tue, May 05, 2009 at 11:55:17AM +0200, Thomas Rast wrote:\n> Fredrik Skolmli wrote:\n> > --- a/Documentation/git-clean.txt\n> > +++ b/Documentation/git-clean.txt\n> > @@ -23,6 +23,9 @@ example, be useful to remove all build products.\n> > If any optional `...` arguments are given, only those paths\n> > are affected.\n> > \n> > +If no arguments are given, the cleaning is recursive, starting at the current\n> > +path.\n> \n> That makes it sound as if the case was not recursive, but it\n> is!\n\nAuch, good point. Any suggestions on how to formulate it?\n\n-- \nFredrik Skolmli\n"},{"id":"113031","messageId":"20090505111707.GC1436@vidovic","threadId":"19184","inReplyTo":"20090505100506.GF27900@frsk.net","subject":"[PATCH] Re: Documentation: Clarify which paths git-clean will affect","fromName":"Nicolas Sebrecht","fromEmail":"nicolas.s.dev@gmx.fr","sentAt":"2009-05-05T11:17:07Z","receivedAt":"2009-05-05T11:17:07Z","isPatch":true,"sender":{"key":"nicolas.s.dev@gmx.fr","avatar":null},"body":"The 05/05/09, Fredrik Skolmli wrote:\n> On Tue, May 05, 2009 at 11:55:17AM +0200, Thomas Rast wrote:\n> > Fredrik Skolmli wrote:\n> > > --- a/Documentation/git-clean.txt\n> > > +++ b/Documentation/git-clean.txt\n> > > @@ -23,6 +23,9 @@ example, be useful to remove all build products.\n> > > If any optional `...` arguments are given, only those paths\n> > > are affected.\n> > > \n> > > +If no arguments are given, the cleaning is recursive, starting at the current\n> > > +path.\n> > \n> > That makes it sound as if the case was not recursive, but it\n> > is!\n> \n> Auch, good point. Any suggestions on how to formulate it?\n\nMaybe:\n\nIf any optional `...` arguments are given, only those paths are\naffected. If no arguments are given, the cleaning starts at the current\npath.\n\nThe cleaning are recursive.\n\n-- \nNicolas Sebrecht\n"},{"id":"113033","messageId":"200905051426.18814.trast@student.ethz.ch","threadId":"19184","inReplyTo":"20090505100506.GF27900@frsk.net","subject":"Re: [PATCH] Documentation: Clarify which paths git-clean will affect","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2009-05-05T12:26:14Z","receivedAt":"2009-05-05T12:26:14Z","isPatch":true,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Fredrik Skolmli wrote:\n> On Tue, May 05, 2009 at 11:55:17AM +0200, Thomas Rast wrote:\n> > That makes it sound as if the case was not recursive, but it\n> > is!\n> \n> Auch, good point. Any suggestions on how to formulate it?\n\nI'm not entirely happy with it, but if we're going to change it, I'd\nput the \"recursive\" near the top to make it more visible. Maybe like\nso:\n\n-- 8< --\ndiff --git i/Documentation/git-clean.txt w/Documentation/git-clean.txt\nindex 43b2de7..3550fc0 100644\n--- i/Documentation/git-clean.txt\n+++ w/Documentation/git-clean.txt\n@@ -13,15 +13,15 @@ SYNOPSIS\n DESCRIPTION\n -----------\n \n-This allows cleaning the working tree by removing files that are not\n+Cleans the working tree by recursively removing files that are not\n under version control.\n \n Normally, only files unknown to git are removed, but if the '-x'\n option is specified, ignored files are also removed. This can, for\n example, be useful to remove all build products.\n \n-If any optional `...` arguments are given, only those paths\n-are affected.\n+If any optional `...` arguments are given, those paths are\n+affected. Otherwise, the cleaning starts at the current directory.\n \n OPTIONS\n -------\n-- >8 --\n\nAs a side note, a random survey among a few other manpages did not\ngive any conclusive advice on the formulation of the first sentence.\nI originally wanted to make it imperative (\"clean the working\ntree...\"), but my perception may be skewed by the commit message\nguidelines.\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"113045","messageId":"7vk54v1py6.fsf@alter.siamese.dyndns.org","threadId":"19184","inReplyTo":"200905051426.18814.trast@student.ethz.ch","subject":"Re: [PATCH] Documentation: Clarify which paths git-clean will affect","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-05-05T16:20:49Z","receivedAt":"2009-05-05T16:20:49Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thomas Rast writes:\n\n> Normally, only files unknown to git are removed, but if the '-x'\n> option is specified, ignored files are also removed. This can, for\n> example, be useful to remove all build products.\n> \n> -If any optional `...` arguments are given, only those paths\n> -are affected.\n> +If any optional `...` arguments are given, those paths are\n> +affected. Otherwise, the cleaning starts at the current directory.\n\nWith or without path limiters, clean does not look outside the current\ndirectory; I think the \"otherwise\" makes things worse than the original.\n\nI'd suggest not touching this paragraph at all, but instead say something\nlike this at the beginning:\n\n> diff --git i/Documentation/git-clean.txt w/Documentation/git-clean.txt\n> index 43b2de7..3550fc0 100644\n> --- i/Documentation/git-clean.txt\n> +++ w/Documentation/git-clean.txt\n> @@ -13,15 +13,15 @@ SYNOPSIS\n> DESCRIPTION\n> -----------\n> \n> -This allows cleaning the working tree by removing files that are not\n> +Cleans the working tree by recursively removing files that are not\n> under version control.\n\n Cleans the working tree by recursively removing files that are not\n under version control, starting from the current directory.\n"},{"id":"113081","messageId":"200905061524.52186.trast@student.ethz.ch","threadId":"19184","inReplyTo":"7vk54v1py6.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: Clarify which paths git-clean will affect","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2009-05-06T13:24:47Z","receivedAt":"2009-05-06T13:24:47Z","isPatch":true,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Junio C Hamano wrote:\n> Thomas Rast writes:\n> \n> > -If any optional `...` arguments are given, only those paths\n> > -are affected.\n> > +If any optional `...` arguments are given, those paths are\n> > +affected. Otherwise, the cleaning starts at the current directory.\n> \n> With or without path limiters, clean does not look outside the current\n> directory; I think the \"otherwise\" makes things worse than the original.\n> \n> I'd suggest not touching this paragraph at all, but instead say something\n> like this at the beginning:\n> \n> > -This allows cleaning the working tree by removing files that are not\n> \n> Cleans the working tree by recursively removing files that are not\n> under version control, starting from the current directory.\n\nIndeed, yours is better.\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"113095","messageId":"20090506163145.GF4452@frsk.net","threadId":"19184","inReplyTo":"200905061524.52186.trast@student.ethz.ch","subject":"Re: [PATCH] Documentation: Clarify which paths git-clean will affect","fromName":"Fredrik Skolmli","fromEmail":"fredrik@frsk.net","sentAt":"2009-05-06T16:31:45Z","receivedAt":"2009-05-06T16:31:45Z","isPatch":true,"sender":{"key":"fredrik@frsk.net","avatar":"https://avatars.githubusercontent.com/u/40261?v=4"},"body":"On Wed, May 06, 2009 at 03:24:47PM +0200, Thomas Rast wrote:\n\n> > I'd suggest not touching this paragraph at all, but instead say something\n> > like this at the beginning:\n> > \n> > > -This allows cleaning the working tree by removing files that are not\n> > \n> > Cleans the working tree by recursively removing files that are not\n> > under version control, starting from the current directory.\n> \n> Indeed, yours is better.\n\nAnd I agree, it does looks better. Junio, would you like me to produce a\npatch v2, or would you like do the honor? (After all, you came up with the\nfinal suggestion)\n\n-- \nFredrik Skolmli\n"},{"id":"113102","messageId":"7vljpauna5.fsf@alter.siamese.dyndns.org","threadId":"19184","inReplyTo":"20090506163145.GF4452@frsk.net","subject":"Re: [PATCH] Documentation: Clarify which paths git-clean will affect","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-05-06T17:57:54Z","receivedAt":"2009-05-06T17:57:54Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Fredrik Skolmli writes:\n\n> On Wed, May 06, 2009 at 03:24:47PM +0200, Thomas Rast wrote:\n>\n>> Indeed, yours is better.\n>\n> And I agree, it does looks better. Junio, would you like me to produce a\n> patch v2, or would you like do the honor? (After all, you came up with the\n> final suggestion)\n\nOk, I'll queue this one.\n\n-- >8 -- \nDate: Wed, 6 May 2009 10:48:26 -0700\nSubject: [PATCH] git-clean doc: the command only affects paths under $(cwd)\n\nFredrik Skolmli and Thomas Rast noticed that it was left unstated that\n\"git clean\" ran from a subdirectory will not affect anything outside it,\nwith or without path limiters.\n\nSigned-off-by: Junio C Hamano \n---\n Documentation/git-clean.txt | 4 ++--\n 1 files changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-clean.txt b/Documentation/git-clean.txt\nindex 43b2de7..be894af 100644\n--- a/Documentation/git-clean.txt\n+++ b/Documentation/git-clean.txt\n@@ -13,8 +13,8 @@ SYNOPSIS\n DESCRIPTION\n -----------\n \n-This allows cleaning the working tree by removing files that are not\n-under version control.\n+Cleans the working tree by recursively removing files that are not\n+under version control, starting from the current directory.\n \n Normally, only files unknown to git are removed, but if the '-x'\n option is specified, ignored files are also removed. This can, for\n"}]}