From: "Geoffrey Irving" <irving@naml.us>
To: "Jeff King" <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: automatically removing missing files beneath a directory
Date: Thu, 8 May 2008 10:19:46 -0700 [thread overview]
Message-ID: <7f9d599f0805081019r16e3b6ahd14d55b7d32c6231@mail.gmail.com> (raw)
In-Reply-To: <20080508171843.GA29607@sigill.intra.peff.net>
On Thu, May 8, 2008 at 10:18 AM, Jeff King <peff@peff.net> wrote:
> On Thu, May 08, 2008 at 10:12:56AM -0700, Geoffrey Irving wrote:
>
>> Cool. "git add -u && git add ." does exactly what I want.
>>
>> This is only indirectly mentioned in the documentation. If you think
>> it's reasonable to mention it more explicitly, I've attached a patch.
>
> Yeah, the term "update" is not really defined there. I actually prefer
> to mention it even earlier in the paragraph; does this make sense to
> you?
>
> diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt
> index 35e67a0..e2389e3 100644
> --- a/Documentation/git-add.txt
> +++ b/Documentation/git-add.txt
> @@ -71,7 +71,9 @@ OPTIONS
> the specified filepatterns before exiting.
>
> -u::
> - Update only files that git already knows about. This is similar
> + Update only files that git already knows about, staging modified
> + content for commit and marking deleted files for removal. This
> + is similar
> to what "git commit -a" does in preparation for making a commit,
> except that the update is limited to paths specified on the
> command line. If no paths are specified, all tracked files in the
Yep, that's better than mine.
Geoffrey
prev parent reply other threads:[~2008-05-08 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 16:39 automatically removing missing files beneath a directory Geoffrey Irving
2008-05-08 16:44 ` Jeff King
2008-05-08 17:12 ` Geoffrey Irving
2008-05-08 17:18 ` Jeff King
2008-05-08 17:19 ` Geoffrey Irving [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=7f9d599f0805081019r16e3b6ahd14d55b7d32c6231@mail.gmail.com \
--to=irving@naml.us \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).