From: "Dmitry Potapov" <dpotapov@gmail.com>
To: "Dmitry Potapov" <dpotapov@gmail.com>,
"Randal L. Schwartz" <merlyn@stonehenge.com>,
git@vger.kernel.org
Subject: Re: Many gits are offline this week
Date: Fri, 5 Oct 2007 21:19:02 +0400 [thread overview]
Message-ID: <37fcd2780710051019l37b3dde2p57f24fef27b62bf6@mail.gmail.com> (raw)
In-Reply-To: <20071005162029.GA18522@old.davidb.org>
> >I believe I have found one mistake in your slides. Slide 18 reads:
> >"git-commit -a" is like "git-add .; git-commit"
> >
> >But it is incorrect, because "git-commit -a" does not add new files, so
> >it works like "git-add -u .; git-commit".
>
> "git-commit -a" also detects files that have been deleted, whereas
> "git-add" does not.
I just tried "git-add -u ." and it *does* detect deleted files.
$ git-status
# On branch master
nothing to commit (working directory clean)
$ rm oldfile
$ git-status
# On branch master
# Changed but not updated:
# (use "git add/rm <file>..." to update what will be committed)
#
# deleted: oldfile
#
no changes added to commit (use "git add" and/or "git commit -a")
$ git-add -u .
$ git-status
# On branch master
# Changes to be committed:
# (use "git reset HEAD <file>..." to unstage)
#
# deleted: oldfile
#
$ git-commit
Created commit 17e2bba: delete
1 files changed, 0 insertions(+), 1 deletions(-)
delete mode 100644 oldfile
So, it works exactly as "git-commit -a" in this case.
Dmitry
next prev parent reply other threads:[~2007-10-05 17:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 1:04 Many gits are offline this week Shawn O. Pearce
2007-10-05 1:27 ` Randal L. Schwartz
2007-10-05 1:36 ` Johannes Schindelin
2007-10-05 1:43 ` Shawn O. Pearce
2007-10-05 1:59 ` alan
2007-10-05 9:14 ` Paolo Ciarrocchi
2007-10-05 13:12 ` Randal L. Schwartz
2007-10-05 14:41 ` Dmitry Potapov
2007-10-05 16:20 ` David Brown
2007-10-05 17:19 ` Dmitry Potapov [this message]
2007-10-05 18:33 ` Jeff King
2007-10-07 17:01 ` Shawn O. Pearce
2007-10-07 19:04 ` Daniel Barkalow
2007-10-07 22:31 ` Johannes Schindelin
2007-10-07 23:09 ` Shawn O. Pearce
2007-10-07 19:37 ` Randal L. Schwartz
2007-10-28 10:07 ` Mike Hommey
2007-10-05 1:43 ` Johannes Schindelin
2007-10-07 4:59 ` Steven Grimm
2007-10-05 15:13 ` Frank Lichtenheld
2007-10-05 20:26 ` Pierre Habouzit
2007-10-06 9:05 ` Lars Hjemli
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=37fcd2780710051019l37b3dde2p57f24fef27b62bf6@mail.gmail.com \
--to=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
/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).