My bad, it seems like this is another issue.

I found this StackOverflow page quite helpful in explaining the hows and whys:
https://stackoverflow.com/questions/4873980/git-diff-says-subproject-is-dirty

Cheers,

Hécate

Le 15/05/2020 à 16:30, Hécate a écrit :

Hi Simon,

I usually manage to get it to disappear by using `git submodule update --recursive`.
Is it a flag you've used in your previous attempts?

Cheers,

Hécate.

Le 15/05/2020 à 16:24, Simon Peyton Jones via ghc-devs a écrit :

No amount of git submodule update makes it go away.  Any ideas?


_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Reply via email to