From: Andreas Schwab <schwab@linux-m68k.org>
To: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
Cc: <git@vger.kernel.org>
Subject: Re: Surprising semantics of "git add file"
Date: Sun, 05 May 2019 22:31:05 +0200 [thread overview]
Message-ID: <87o94gbq46.fsf@igel.home> (raw)
In-Reply-To: <5CCF414A020000A10003108C@gwsmtp.uni-regensburg.de> (Ulrich Windl's message of "Sun, 05 May 2019 22:02:18 +0200")
On Mai 05 2019, "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de> wrote:
> After that a "git diff --cached file" just shows the changes added interactively, but when I "git add file" to commit those changes), even the unstaged changes from file are committed.
Did you really mean "git add" here? It doesn't commit, it adds to the index.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2019-05-05 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 20:02 Surprising semantics of "git add file" Ulrich Windl
2019-05-05 20:12 ` Antw: " Ulrich Windl
2019-05-05 20:31 ` Andreas Schwab [this message]
2019-05-06 7:14 ` Antw: " Ulrich Windl
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=87o94gbq46.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=git@vger.kernel.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 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).