{"thread":{"id":"32114","subject":"v1.8.0-150-gb0b00a3: Weird documentation for git-rm","startedAt":"2012-11-14T18:15:29Z","lastAt":"2012-11-14T18:50:51Z","messageCount":3,"participants":["Horst H. von Brand","Matt Kraai"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"203206","messageId":"201211141815.qAEIFTBi017644@netbook1.inf.utfsm.cl","threadId":"32114","inReplyTo":null,"subject":"v1.8.0-150-gb0b00a3: Weird documentation for git-rm","fromName":"Horst H. von Brand","fromEmail":"vonbrand@inf.utfsm.cl","sentAt":"2012-11-14T18:15:29Z","receivedAt":"2012-11-14T18:15:29Z","isPatch":false,"sender":{"key":"vonbrand@inf.utfsm.cl","avatar":"https://avatars.githubusercontent.com/u/211384?v=4"},"body":"The file Documentation/git-rm.txt says:\n\n---8><---- 8><-------\nUsing ``git add -A''\n~~~~~~~~~~~~~~~~~~~~\nWhen accepting a new code drop for a vendor branch, you probably\nwant to record both the removal of paths and additions of new paths\nas well as modifications of existing paths.\n\nTypically you would first remove all tracked files from the working\ntree using this command:\n\nSubmodules\n~~~~~~~~~~\n---8><---- 8><-------\n\nI believe a command is missing here.\n\nThe explanation also leaves me scratching my head...\n\n(In Fedora's git-1.7.7.6-1.fc16.x86_64 there is a command and some further\nexplanation).\n-- \nDr. Horst H. von Brand User #22616 counter.li.org\nDepartamento de Informatica Fono: +56 32 2654431\nUniversidad Tecnica Federico Santa Maria +56 32 2654239\nCasilla 110-V, Valparaiso, Chile 2340000 Fax: +56 32 2797513\n"},{"id":"203207","messageId":"1352918944-26606-1-git-send-email-kraai@ftbfs.org","threadId":"32114","inReplyTo":"201211141815.qAEIFTBi017644@netbook1.inf.utfsm.cl","subject":"[PATCH] docs: move submodule section","fromName":"Matt Kraai","fromEmail":"kraai@ftbfs.org","sentAt":"2012-11-14T18:49:04Z","receivedAt":"2012-11-14T18:49:04Z","isPatch":true,"sender":{"key":"kraai@ftbfs.org","avatar":null},"body":"293ab15e (\"submodule: teach rm to remove submodules unless they\ncontain a git directory\", 2012-09-26) inserted the \"Submodules\"\nsection between a sentence describing a command and the command. Move\nthe \"Submodules\" section further down.\n\nSigned-off-by: Matt Kraai \n---\n Documentation/git-rm.txt | 30 +++++++++++++++---------------\n 1 files changed, 15 insertions(+), 15 deletions(-)\n\ndiff --git a/Documentation/git-rm.txt b/Documentation/git-rm.txt\nindex 882cb11..262436b 100644\n--- a/Documentation/git-rm.txt\n+++ b/Documentation/git-rm.txt\n@@ -107,21 +107,6 @@ as well as modifications of existing paths.\n Typically you would first remove all tracked files from the working\n tree using this command:\n \n-Submodules\n-~~~~~~~~~~\n-Only submodules using a gitfile (which means they were cloned\n-with a git version 1.7.8 or newer) will be removed from the work\n-tree, as their repository lives inside the .git directory of the\n-superproject. If a submodule (or one of those nested inside it)\n-still uses a .git directory, `git rm` will fail - no matter if forced\n-or not - to protect the submodule's history.\n-\n-A submodule is considered up-to-date when the HEAD is the same as\n-recorded in the index, no tracked files are modified and no untracked\n-files that aren't ignored are present in the submodules work tree.\n-Ignored files are deemed expendable and won't stop a submodule's work\n-tree from being removed.\n-\n ----------------\n git ls-files -z | xargs -0 rm -f\n ----------------\n@@ -149,6 +134,21 @@ use the following command:\n git diff --name-only --diff-filter=D -z | xargs -0 git rm --cached\n ----------------\n \n+Submodules\n+~~~~~~~~~~\n+Only submodules using a gitfile (which means they were cloned\n+with a git version 1.7.8 or newer) will be removed from the work\n+tree, as their repository lives inside the .git directory of the\n+superproject. If a submodule (or one of those nested inside it)\n+still uses a .git directory, `git rm` will fail - no matter if forced\n+or not - to protect the submodule's history.\n+\n+A submodule is considered up-to-date when the HEAD is the same as\n+recorded in the index, no tracked files are modified and no untracked\n+files that aren't ignored are present in the submodules work tree.\n+Ignored files are deemed expendable and won't stop a submodule's work\n+tree from being removed.\n+\n EXAMPLES\n --------\n `git rm Documentation/\\*.txt`::\n-- \n1.7.2.5\n"},{"id":"203208","messageId":"20121114185051.GB20412@ftbfs.org","threadId":"32114","inReplyTo":"1352918944-26606-1-git-send-email-kraai@ftbfs.org","subject":"Re: [PATCH] docs: move submodule section","fromName":"Matt Kraai","fromEmail":"kraai@ftbfs.org","sentAt":"2012-11-14T18:50:51Z","receivedAt":"2012-11-14T18:50:51Z","isPatch":true,"sender":{"key":"kraai@ftbfs.org","avatar":null},"body":"On Wed, Nov 14, 2012 at 10:49:04AM -0800, Matt Kraai wrote:\n> 293ab15e (\"submodule: teach rm to remove submodules unless they\n> contain a git directory\", 2012-09-26) inserted the \"Submodules\"\n> section between a sentence describing a command and the command. Move\n> the \"Submodules\" section further down.\n> \n> Signed-off-by: Matt Kraai \n\nSorry, I amended the patch to include a Reported-by line but forgot to\nreformat it before sending. It should have included:\n\n Reported-by: \"Horst H. von Brand\" \n\n-- \nMatt Kraai\nhttps://ftbfs.org/kraai\n"}]}