david@lang.hm writes:Committing the change? Yes, once he commits. As long as git keeps files tracked in that directory, there is no reason for it to delete it. I agree that it is hard to come up with a good logic for this sort of thing. git-add checks the _current_ state of a file into the index. git-rm can actually do the same only by actually _deleting_ the working copy. So when should git try deleting the directory? Probably when the directory becomes empty in the index, for consistency. Too bad that the index does not contain any information about directories at all, so there is no good way to figure this particular point in time out efficiently. I guess that git rather attempts deleting the directory when the tree in the _repository_ rather than the index becomes empty. And for that you need to commit. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| David Newall | Re: Slow DOWN, please!!! |
| Peter Zijlstra | [PATCH 00/23] per device dirty throttling -v8 |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
git: | |
