> On May 25, 2016, at 4:25 PM, Sam Tobin-Hochstadt <[email protected]> wrote: > > When we split the Racket repository out into many smaller > repositories, we were quite aggressive -- just about everything moved > out. At this point, it's clear that we were a little too aggressive. > In particular, the `net` and `compiler` repositories have been uneasy > as separate entities. Their docs are in the wrong places, and they > often have to change in coordination with the main repo. So we're > going to merge them back in. > > You can see how this will work in this pull request: > https://github.com/racket/racket/pull/1332 > > The resulting repository will have multiple root commits. I don't > think this is a problem, but it can perhaps be fixed if needed. > > Once this is done, previously cloned versions of those repositories > won't update. To address this, run the following command now, unless > you absolutely need the clone versions: > > $ raco pkg update --lookup net compile > > I plan to merge this in the next couple days. >
Could you explain to the uninitiated what the meaning of the result is? > % raco pkg update --lookup net compile > raco pkg update: package not currently installed > package: compile > current scope: installation Next, does the “won’t update” mean we have to clone a completely new version? What do I do with un-pushed commits? (I am not ready to push.) Thanks — Matthias -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/2D26007F-587F-4726-808B-A6CB3515EF54%40ccs.neu.edu. For more options, visit https://groups.google.com/d/optout.
