ghc github.com help...

[Karel Gardas]

Hello Johan,

On 07/12/11 03:48 PM, Johan Tibell wrote:
> On Tue, Jul 12, 2011 at 3:34 PM, Karel Gardas<karel.gardas at centrum.cz>  wrote:
>> Hello,
>>
>> I've forked ghc/ghc repo on github.com to work on ARM port. Now I'd like to
>> check it out and compile it, but I'm not able to `sync-all get' since git
>> complains with `warning: remote HEAD refers to nonexistent ref, unable to
>> checkout.'
>>
>> I've also tested:
>> perl ./sync-all -r http://darcs.haskell.org/git get
>>
>> in a desperate attempt that git will get all the packages from haskell.org,
>> but the result is still the same.
>>
>> May I ask how the people here are using github.com for their GHC
>> development?
>
> I tested this a moment ago and this works:
>
>      git clone https://github.com/ghc/ghc.git
>      cd ghc
>      ./sync-all get

indeed, this is working. But I've set my fork as recommended on 
Github's.com page: http://help.github.com/fork-a-repo/ -- the fork is:

https://github.com/kgardas/ghc.git

and if you get it, then sync-all fails with:

./sync-all get
== running git config core.ignorecase true
== running git clone https://github.com/kgardas/ghc-tarballs.git 
ghc-tarballs
Too many arguments.

usage: git clone [options] [--] <repo> [<dir>]

     -v, --verbose         be more verbose
     -q, --quiet           be more quiet
     --progress            force progress reporting
     -n, --no-checkout     don't create a checkout
     --bare                create a bare repository
     --mirror              create a mirror repository (implies bare)
     -l, --local           to clone from a local repository
     --no-hardlinks        don't use local hardlinks, always copy
     -s, --shared          setup as shared repository
     --recursive           initialize submodules in the clone
     --recurse-submodules  initialize submodules in the clone
     --template <template-directory>
                           directory from which templates will be used
     --reference <repo>    reference repository
     -o, --origin <branch>
                           use <branch> instead of 'origin' to track 
upstream
     -b, --branch <branch>
                           checkout <branch> instead of the remote's HEAD
     -u, --upload-pack <path>
                           path to git-upload-pack on the remote
     --depth <depth>       create a shallow clone of that depth

git failed: 33024 at ./sync-all line 206.
== Checking for old haddock repo
== Checking for old binary repo


I'm sorry, but perhaps my previous failure might also be caused by wrong 
CA path setup.

> You'll also want to add your fork as a remote so you can push work to it:
>
>      git remote add tibbe git at github.com:tibbe/ghc.git

Oh, so you get ghc/ghc.git and work on it and then push to your fork? 
I've thought the model should be reversed: get your form and push to it 
(and sometime merge from "upstream").

Thanks!
Karel