From: Salikh Zakirov <salikh@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-commit goes awry after git-add -u
Date: Wed, 15 Aug 2007 23:21:48 +0900 [thread overview]
Message-ID: <f9v266$uph$2@sea.gmane.org> (raw)
In-Reply-To: <f9v1t6$uph$1@sea.gmane.org>
Salikh Zakirov wrote:
> Alternative sequence of commands, not involving 'git-add -u' produces
> correct results (without output for compactness)
> $ git add vm/em
> $ git rm -r vm/vmcore/src/util/ipf
> $ git rm -r vm/vmcore/src/util/em64t
> $ git rm -r vm/em/src/ia32
Sorry, forgot an important command in the sequence:
$ git commit -m moved
> $ git status
> # On branch master
> nothing to commit (working directory clean)
next prev parent reply other threads:[~2007-08-15 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 14:16 git-commit goes awry after git-add -u Salikh Zakirov
2007-08-15 14:21 ` Salikh Zakirov [this message]
2007-08-15 20:49 ` Junio C Hamano
2007-08-15 21:12 ` [PATCH] Fix "git add -u" data corruption Junio C Hamano
2007-08-16 0:15 ` Zakirov Salikh
2007-08-15 23:43 ` git-commit goes awry after git-add -u Salikh Zakirov
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='f9v266$uph$2@sea.gmane.org' \
--to=salikh@gmail.com \
--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).