Jeff King <peff@xxxxxxxx> writes: > On Tue, Feb 27, 2007 at 02:23:02AM -0800, Junio C Hamano wrote: > >> Although pointers to component project commits are represented >> as "parent" field in commit objects, I suspect that you wish >> they were treated as if they were tree objects contained in the >> toplevel commits more often than not for the purposes of many >> git operations. > > Yes, that is exactly correct. One problem I realized after doing this is > that you get unexpected results from "git-whatchanged -- subproject/". > My first expectation was to see _just_ the history of the subproject. > But of course, you see only the merge commit, since the previous commits > for that subproject didn't have that path at all (they were in the > root!). Subproject support would fix that, as would simply rewriting > the history. For the record, I am aware of the fact that the recent git.git itself exhibits this exact problem, due to the subtree merge of git-gui repository. I haven't got to the point of being annoyed enough to regret it, but running "git show" on merges from Shawn always needs -M option to make heads or tails of. - 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