2008/6/25 Karl Hasselström <kha@xxxxxxxxxxx>: > And in the process, make it more powerful: it will now first create a > temp patch containing the updates, and then try to merge it into the > patch to be updated. If that patch is applied, this is done by > popping, pushing, and coalescing; if it is unapplied, it is done with > an in-index merge. Does it make sense to refresh an unapplied patch? Maybe adding a new file to the patch but I don't really see a need for this. > Also, whenever path limiting is used, we will now use a temporary > index in order to avoid including all staged updates (since they may > touch stuff outside the path limiters). I haven't checked but what is the behaviour in subdirectors? It currently refreshes everythink unless "." is specified so that it will only refresh the current subdirectory. The patch looks fine otherwise. -- Catalin -- 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
