Hi Ian, since you have pinned a commit that is on a branch, people whose clones do not track that branch will never see the commit: $ ( cd libraries/random ; git remote show; git remote show origin ) origin * remote origin Fetch URL: https://github.com/ghc/packages-random.git Push URL: https://github.com/ghc/packages-random.git HEAD branch: master Remote branch: master tracked Local ref configured for 'git push': master pushes to master (up to date) This may be the problem what we see. Possibly the 'sync-all' script could be amended, so that your 'ghc-head' branch is added to the remote? Cheers, Gabor On 2/5/13, Ian Lynagh <igloo@earth.li> wrote:
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/6a46b4627d4f3f81d65bf6b5b5c0bc...
---------------------------------------------------------------
commit 6a46b4627d4f3f81d65bf6b5b5c0bcf86607c463 Author: Ian Lynagh <ian@well-typed.com> Date: Tue Feb 5 14:08:05 2013 +0000
Add the new random commit again
---------------------------------------------------------------
libraries/random | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/libraries/random b/libraries/random index 69bfde2..2117e38 160000 --- a/libraries/random +++ b/libraries/random @@ -1 +1 @@ -Subproject commit 69bfde219bab869729fdbe9c1496371f912bf41e +Subproject commit 2117e38729adaa4f465f3c5b7a8c5c4d77702d3f
_______________________________________________ ghc-commits mailing list ghc-commits@haskell.org http://www.haskell.org/mailman/listinfo/ghc-commits