On Fri, Aug 28, 2009 at 03:05:31PM -0400, Jeff King wrote: > For the index case, we unfortunately cannot represent the situation in > the index using a tree, which means we cannot have a stash that doesn't > lose information. So we have to choose either dropping those index > entries, inserting them as blank files, or inserting them with > working-tree contents. Actually, you _could_ try representing the information by shoe-horning it into the tree. For example, by allocating a bit of the mode as "intent-to-add". That seems pretty ugly to me, though. You could also try to stick the information in the stash's commit message and recreate it during "stash apply". But again, that feels kind of ugly. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html