From: "Shak" <sshaikh@hotmail.com>
To: git@vger.kernel.org
Subject: Re: Deleting files
Date: Thu, 12 Jun 2008 13:01:01 +0100 [thread overview]
Message-ID: <g2r36d$2ju$1@ger.gmane.org> (raw)
In-Reply-To: <g2r1sb$tut$1@ger.gmane.org>
"Shak" <sshaikh@hotmail.com> wrote in message
news:g2r1sb$tut$1@ger.gmane.org...
> "Shak" <sshaikh@hotmail.com> wrote in message
> news:g2r19e$s6e$1@ger.gmane.org...
>> Hi,
>>
>> Are files supposed to be continually tracked after commiting after
>> deleting them?
>>
>> git status reports that files have been deleted as expected (they're not
>> there anymore). I commit as wanted. I do some more work, but then git
>> status still reports that the same files have been deleted. As such I
>> have a historical list of "deleted" files that I may have been working on
>> previously and had committed.
>>
>> I have to run git rm to erase these entries, but I've no idea how that
>> affects my history.
>>
>> Shouldn't git add/commit remember that a file has been deleted
>> previously?
>>
>> On a related note, once I do git rm on one of these files, git status
>> sometimes reports that these rm'd files have been renamed to a new one
>> instead! What's going on? :(
>
> To be clear on the last point, git seems to be incorrectly detecting that
> I've copied (sometimes to the same directory) and renamed files. What's
> the difference anyway? And is there anyway to override it's overzelaous
> assumptions?
>
To rudely reply to my own message a second time, it seems I have to
explicitly run "git add -u" to actually commit deletions before committing.
I don't notice any changes in "git status" so there doesn't seem a way of
knowing that it's required.
I've also noticed that renames aren't detected until you commit a delete.
This is all becoming very counter-intuitive :(
Shak
next prev parent reply other threads:[~2008-06-12 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 11:28 Deleting files Shak
2008-06-12 11:38 ` Shak
2008-06-12 12:01 ` Shak [this message]
2008-06-12 12:11 ` Pieter de Bie
2008-06-12 12:23 ` Shak
2008-06-12 20:44 ` Alex Riesen
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='g2r36d$2ju$1@ger.gmane.org' \
--to=sshaikh@hotmail.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).