Re: Recursive remove
- From
Junio C Hamano <junkio@cox.net>
- Date
- Jan 13, 2006, 19:51 UTC
- Message-ID
- <7vslrr6h4z.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <BAYC1-PASMTP08F3875A7636E18401E7B3AE260@CEZ.ICE>
sean <seanlkml@sympatico.ca> writes:
Show 8 quoted lines
> On Fri, 13 Jan 2006 09:37:54 -0800 > Junio C Hamano <junkio@cox.net> wrote: >> >> $ rm -fr Some/Dir; git commit -a -m 'Remove' >> >> perhaps? > > Sigh, its been a humbling morning all around; can't get easier than that.
Perhaps this is because I did not do a good job in Documentation/git-commit.txt. Something like this?
-- >8 -- Documentation: git-commit -a
A bit more elaboration on what "update all paths" means.
Signed-off-by: Junio C Hamano <junkio@cox.net>
---
diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt index e0ff74f..e35984d 100644 --- a/Documentation/git-commit.txt +++ b/Documentation/git-commit.txt @@ -25,7 +25,9 @@ information. OPTIONS ------- -a|--all:: - Update all paths in the index file. + Update all paths in the index file. The command with this flag + notices files that have been modified and deleted, but new files + you have not told about git are not affected. -c or -C <commit>:: Take existing commit object, and reuse the log message