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

Re: [PATCH] Documentation/git-clean: Document --force --force

From
SBSoren Brinkmann <soren.brinkmann@xilinx.com>
Date
Dec 20, 2012, 23:37 UTC
Message-ID
<335802a0-38b5-4cbc-9e52-92c92083119e@VA3EHSMHS005.ehs.local>
In-Reply-To
<b48ad5f0-25f7-45c3-b2dc-c0c01645a247@CO9EHSMHS031.ehs.local>
Ping?
On Thu, Dec 13, 2012 at 05:46:55PM -0800, Soren Brinkmann wrote:
Show 42 quoted lines
> This patch documents the behavior of 'git clean' when
> encountering nested git repositories.
> Such repositories are only deleted if '-f' is passed twice
> to 'git clean'.
> 
> Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
> ---
>  Documentation/git-clean.txt | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/git-clean.txt b/Documentation/git-clean.txt
> index 9f42c0d..0b31454 100644
> --- 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.
>  
> +Nested git repositories are not removed unless the '-f' option is
> +passed to 'git clean' twice.
> +
>  OPTIONS
>  -------
>  -d::
> @@ -35,6 +38,8 @@ OPTIONS
>  --force::
>  	If the git configuration variable clean.requireForce is not set
>  	to false, 'git clean' will refuse to run unless given -f or -n.
> +	Pass this option twice to 'git clean' in order to also remove
> +	nested git repositories.
>  
>  -n::
>  --dry-run::
> -- 
> 1.8.0.2
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
Previous: Soren BrinkmannNext: Junio C Hamano
Message 2 of 4 in “Documentation/git-clean: Document --force --force”
  1. Documentation/git-clean: Document --force --forceSoren Brinkmann, Dec 14, 2012
  2. Soren BrinkmannDec 20, 2012
  3. Junio C HamanoDec 21, 2012
  4. Soren BrinkmannDec 21, 2012

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.