4 ms·
Sounds interesting, however it lacks specifications/documentation. In particular, I'd like to know what happens with commits that touch paths across subtrees.
by lysium 17y ago
Sounds interesting, however it lacks specifications/documentation.
In particular, I'd like to know what happens with commits that touch paths across subtrees. IMHO, this is the most interesting use case, because otherwise, I'd just extract the commits touching the subdirectory of the subtree with git-log.
Skimming over the source, I don't think git-subtree handles commits across subtrees at all, but I hope I am wrong.
- wingo 17y agoA sane thing to do would be to keep the commit log, but only the changes to the subtree in question. However, though I am not a bad sh programmer, at some point my brain turned off reading that code.
- psranga 17y agoEven if it didn't handle commits across subtrees, I would still find this useful. I would be ok if this (or an addon) tool detected commits that that spanned subprojects and invited me to split that commit. IMHO, the correct workflow should be: check in modifications to the library subtree and to the library's client in different commits.