David Kastrup <dak@gnu.org> wrote:Yes. But when you read that tree into the index later (by say checking out a branch that points to it) the empty directories will not be created, as they have no files to cause their creation. Committing changes on that branch will remove the empty directories. ;-) Oh, and the above question from you sounds like you think you can modify the last commit to include new directories that weren't there before. You cannot do that without changing the tree SHA-1, which will cause the commit SHA-1 to change. That in turns means you are not actually adding to the last commit but instead are creating an entirely different commit. History in Git is always immutable. -- Shawn. - 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
| Rafael J. Wysocki | [Bug #10493] mips BCM47XX compile error |
| Ingo Molnar | [patch 02/13] syslets: add syslet.h include file, user API/ABI definitions |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Andrea Arcangeli | [PATCH 00 of 11] mmu notifier #v16 |
git: | |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Linus Torvalds | Re: [GIT]: Networking |
| Mark Lord | Re: [BUG] New Kernel Bugs |
