On Mon, Jul 26, 2010 at 10:36 AM, Bryan Larsen <bryan.larsen@xxxxxxxxx> wrote:
>
> To me, that's what git-subtree is: an internal private mirror of an external
> repo. Using git submodule moves that into a separately managed repo, which
> is just unnecessary hassle. Why maintain repo called "clone of library X
> for project A" when you can just stick it inside of project A without any
> downsides?
Without any downsides?
What about merging? What about complex history? IOW, what about
_anything_ but a few extra one-liner patches?
Background: the only time I ever used CVS modules, we had submodules
for things like gcc, binutils, etc. And maintained them separately
from upstream for _years_. Not with some simple one-liner fixes, but
with big fundamental changes that couldn't be sent upstream (and
wouldn't have been accepted anyway) etc.
THAT is the problem space. Not "just a mirror of another project".
Linus
--
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