From: "Shawn O. Pearce" <spearce@spearce.org>
To: Miles Bader <miles@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: way to automatically add untracked files?
Date: Sun, 5 Aug 2007 00:13:20 -0400 [thread overview]
Message-ID: <20070805041320.GH9527@spearce.org> (raw)
In-Reply-To: <fc339e4a0708042100jdf0a0f1jd1fddfb5dc1c1052@mail.gmail.com>
Miles Bader <miles@gnu.org> wrote:
> I previously wrote
> > One thing I often want to do is git-add all untracked files, and also
> > automatically git-rm all "disappeared" files
> ...
> > One way to do this seems to be just "git add ."
>
> Oh, also, "git add ." doesn't seem to do the right thing with
> "dissapeared" files: If I do:
>
> mv foo.cc bar.cc
> git add .
Right. Who wants "add" to actually mean "add and delete"?
Shouldn't that be then called "git-add-and-rm"?
We recently talked about this on the mailing list and decided that
git-add shouldn't remove files that have disappeared, as doing so
might break most user's expections of what git-add does.
> then git-status will show a new file "bar.cc", but will list "foo.cc"
> as "deleted " in the "Changed but not updated" section. Perhaps the
> right thing will happen if I do "git-commit -a" (though I don't know,
> I don't really want to try it),
"git commit -a" will remove disappeared files. It has for quite
some time.
> this still results in incorrect
> "git-diff --cached" output (it shows bar.cc as a new file, not as a
> rename of foo.cc).
>
> Am I doing something wrong, or is this just missing functionality?
Try adding the -M option to "git-diff". That will enable the rename
detection, and show the rename you are looking to see.
--
Shawn.
next prev parent reply other threads:[~2007-08-05 4:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 3:31 way to automatically add untracked files? Miles Bader
2007-08-05 3:58 ` Shawn O. Pearce
2007-08-05 4:13 ` Junio C Hamano
2007-08-05 4:00 ` Miles Bader
2007-08-05 4:13 ` Shawn O. Pearce [this message]
2007-08-05 4:22 ` Miles Bader
2007-08-05 4:23 ` Junio C Hamano
2007-08-05 4:30 ` Miles Bader
2007-08-05 4:39 ` Junio C Hamano
2007-08-05 4:53 ` Miles Bader
2007-08-05 5:04 ` Junio C Hamano
2007-08-05 5:17 ` Miles Bader
2007-08-05 5:23 ` Johannes Schindelin
2007-08-05 5:27 ` Miles Bader
2007-08-05 11:22 ` Steffen Prohaska
2007-08-05 12:11 ` Johan Herland
2007-08-05 12:17 ` David Kastrup
2007-08-05 16:11 ` Theodore Tso
2007-08-05 19:16 ` Johan Herland
2007-08-06 0:00 ` Miles Bader
2007-08-06 0:16 ` Johannes Schindelin
2007-08-06 3:09 ` Miles Bader
2007-08-06 3:21 ` Johannes Schindelin
2007-08-06 3:45 ` Miles Bader
2007-08-06 7:46 ` Johan Herland
2007-08-06 12:17 ` Johannes Schindelin
2007-08-05 20:04 ` Steffen Prohaska
2007-08-06 0:17 ` Johannes Schindelin
2007-08-06 4:58 ` Steffen Prohaska
2007-08-06 0:32 ` Jakub Narebski
2007-08-06 7:30 ` Johan Herland
2007-08-06 8:45 ` Junio C Hamano
2007-08-06 18:19 ` David Kastrup
2007-08-07 0:08 ` Miles Bader
2007-08-05 5:03 ` Linus Torvalds
2007-08-05 5:14 ` Junio C Hamano
2007-08-05 7:32 ` David Kastrup
2007-08-05 10:33 ` Benchmarking git-add vs git-ls-files+update-index (was: way to automatically add untracked files?) David Kastrup
2007-08-05 7:34 ` way to automatically add untracked files? Miles Bader
2007-08-05 17:04 ` Linus Torvalds
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=20070805041320.GH9527@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=miles@gnu.org \
/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.