On 2013-07-31 00:04:20 -0400, Asumu Takikawa wrote:
> Maybe I will try this with Typed Racket somewhere and see what happens.
One downside I discovered immediately after trying to set this up:
the subtree command is only available in git 1.7.11 and newer and it's
only available if the "contrib" to
On 2013-07-30 17:44:37 -0400, Carl Eastlund wrote:
> 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.
AFAIK, you are correct. OTOH, I imagine that
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 onl
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
A report from the junior varsity squad:
I just tried this on OS X and it worked AOK.
FWIW I've been strictly doing `git pull --ff-only upstream master` to
keep my fork's master 100% in sync with PLT's. Any experimentation or
feature requests done solely on topic branches. (Like I wrote about
here
5 matches
Mail list logo
