Fix get the code

[ahgittin]

Address @rdowner 's comments on #1

[richardcloudsoft]

Something I have just discovered worth noting! If you already have forks, this command still works - your fork is left alone but it still sets up the new remote.

[richardcloudsoft]

Thanks @ahgittin, this improves usability(readability!) a lot. There's still some issues remaining, but IMO it's worth publishing these changes ASAP so I'm going to merge now and regenerate the main website.

[richardcloudsoft]

Some things to add after my experiences with submodules...

I think that this command is necessary after the first git submodule update:

git submodule foreach "git checkout master"

Apache committers may benefit from these commands - it overrides the pushDefault (which is origin, or my personal fork) for the master branch to be the canonical Apache repo, so a simple git push on master will go to the canonical repo. (On the other hand, there's a good argument for not doing this, and requiring the apache-git remote name to be explicitly specified, to avoid accidentally pushing to the wrong place...)

git config branch.master.pushRemote apache-git
git submodule foreach "git config branch.master.pushRemote apache-git"

[ahgittin]

@richardcloudsoft I've applied and pushed the essential changes in fce745e .

Regarding apache-git as the default push target -- I really do not want that. I'm irritated as it is that the new version of git caches my password! I like the extra checks. Though now that force push is allowed it's not quite so grave.

As for the other comments I could go either way. Probably slightly prefer it as it is, longwinded but thorough, but happy if someone cleans it up further. (OTOH removing the script to make it like this is was a great suggestion! Thanks.)

[richardcloudsoft]

Ok that's great, I think we're done for now. Thanks for taking the time to make the changes - I think it's made the first (developer) contact much more straightforward!