I looked into git-subtree, and as I recall it, nothing in the setup recalls what subtree is used for what. Every git-subtree command you enter has to be fully explicit, which is a big hassle. Whereas git-submodule saves its state in the repository, so it knows what it's being used for and you only need to do it once. Hopefully I misunderstood git-subtree, but if I didn't, I found its interface disappointing.
Carl Eastlund On Tue, Jul 30, 2013 at 5:41 PM, Asumu Takikawa <as...@ccs.neu.edu> wrote: > On 2013-07-27 07:10:54 -0600, Matthew Flatt wrote: > > I'm still unsure that submodules are going to be useful for managing a > > kind of "main-distribution" repository with references to package > > repositories. > > Perhaps it would be worth considering using the git subtree feature > instead of submodules for the rest of the repository (just to clarify, > I'm not saying we should reconsider submodules for native-pkgs). > > Description here: > > https://github.com/apenwarr/git-subtree/blob/master/git-subtree.txt > > In particular, this aspect seems useful for us: > "you can also extract the entire history of a subdirectory from > your project and make it into a standalone project" > > From what I understand (not having used them yet), subtrees also enable > end users of our main repo to just do a clone without any special > consideration for the subtrees. Only package maintainers would have to > occasionally update the subtrees in the main repo to pull in changes > from their own package repos. > > Cheers, > Asumu > _________________________ > Racket Developers list: > http://lists.racket-lang.org/dev >
_________________________ Racket Developers list: http://lists.racket-lang.org/dev
