[GHC] #8667: sync-all doesn't work properly if you run from a fork on github

GHC ghc-devs at haskell.org
Mon Jan 13 23:36:46 UTC 2014


#8667: sync-all doesn't work properly if you run from a fork on github
------------------------------------+-------------------------------------
       Reporter:  schyler           |             Owner:  hvr
           Type:  bug               |            Status:  new
       Priority:  normal            |         Milestone:
      Component:  Trac & Git        |           Version:  7.6.3
       Keywords:                    |  Operating System:  Unknown/Multiple
   Architecture:  Unknown/Multiple  |   Type of failure:  None/Unknown
     Difficulty:  Unknown           |         Test Case:
     Blocked By:                    |          Blocking:
Related Tickets:                    |
------------------------------------+-------------------------------------
 The intuitive behaviour when working with projects on github is to make
 your own fork so that you can use the online interface (or GitHub for
 {windows,osx} apps).

 One would assume that this behaviour was endorsed because of the ~130
 forks to the ghc repo, however forking the repo actually causes ./sync-all
 to stop working (it asks for a username and password to whomever@
 github.com). It seems the only way for a person to work with the project
 from github is to clone directly from the original repo.

 This sounds like a bug.

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8667>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler


More information about the ghc-tickets mailing list