From: Junio C Hamano <junkio@cox.net>
To: sean <seanlkml@sympatico.ca>
Cc: git@vger.kernel.org
Subject: Re: Recursive remove
Date: Fri, 13 Jan 2006 11:51:24 -0800 [thread overview]
Message-ID: <7vslrr6h4z.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: BAYC1-PASMTP08F3875A7636E18401E7B3AE260@CEZ.ICE
sean <seanlkml@sympatico.ca> writes:
> 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
prev parent reply other threads:[~2006-01-13 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 13:21 Recursive remove Peter Eriksen
2006-01-13 14:03 ` sean
2006-01-13 14:03 ` sean
2006-01-13 17:37 ` Junio C Hamano
2006-01-13 17:56 ` sean
2006-01-13 17:56 ` sean
2006-01-13 19:51 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vslrr6h4z.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.