I have completed the Git mirror of FPC - well 90% really. What remains is the branches.

Out of the list below, which branches are actually being used? Must I make them all available in the git mirror, or maybe just a few like: fixes_2_2, trunk etc. and probably the release tag ones?

Notes and Info:
----------------
* Unlike what I have done with the Lazarus mirror, the FPC git mirror "master" branch is currently tracking Trunk (from SubVersion). The idea of using "upstream" seems to have confused users in the Lazarus mirror, so I wasn't going to repeat that here.

* The git URL is:
git://github.com/graemeg/freepascal.git

* To view the repository online with your Web Browser go to: http://github.com/graemeg/freepascal/tree/master

* The complete clone of the mirror repository is a 54.5MB download which contains the whole history of FPC's repository - some 13,376 revisions.

* When the repository is cloned, it will unpack locally to around 218MB. I believe this is much smaller than SubVersion single revision checkout.

Enjoy! :-)

=======================
$ git branch -a
* master
remotes/aspect
remotes/avr
remotes/cleanroom
remotes/cpstr
remotes/ctypes
remotes/fixes_2_0
remotes/fixes_2_2
remotes/fixes_2_2_0_dos
remotes/florian
remotes/fpc_2_3
remotes/generics
remotes/genfunc
remotes/inline
remotes/janbruns
remotes/linker

remotes/llvm
remotes/merged
remotes/newthreading
remotes/objc
remotes/rc_2_2_2
remotes/release_2_1_2x
remotes/release_2_2_4_rc1
remotes/resources
remotes/ssa
remotes/tags/release_2_0_0
remotes/tags/release_2_0_2
remotes/tags/release_2_0_4
remotes/tags/release_2_0_4_macos
remotes/tags/release_2_0_4_rc1
remotes/tags/release_2_0_4_rc2
remotes/tags/release_2_0_4_rc3
remotes/tags/release_2_1_2
remotes/tags/release_2_1_4
remotes/tags/release_2_2_0
remotes/tags/release_2_2_2
remotes/tags/release_2_2_2_rc1
remotes/tags/release_2_2_2_rc2
remotes/tags/release_2_2_4
remotes/tags/test_2_0_4
remotes/tags/test_2_0_4_1
remotes/trunk
remotes/tue
remotes/unicodertl
remotes/unicodestring
remotes/unitrw
remotes/wpo
=======================

Regards,
- Graeme -

Great !

And it does work with http://....

Thanks,

Did you also install the ssh+gig://username stuff, which would allow for a much faster download ? If yes which username and password should be used ?

Thanks again,
-Michael

Michael Schnell wrote

And it does work with http://....

Yes, but we warned it is slow. The git protocol is a LOT faster than HTTP.

   $ git clone http://github.com/graemeg/freepascal.git

<quote>
Github supports cloning using both the git protocol over port 9418 and HTTP over port 80. Using the later is very slow (Reference - see url below). You should open port 9418 on your firewall or use HTTP cloning otherwise.
</quote>

http://github.com/blog/92-http-cloning

Did you also install the ssh+gig://username stuff, which would allow for

The repository is hosted on GitHub's servers, so I don't have any control over what can be installed or not. I would suggest you ask you admin to open up port 9418 on the firewall instead - I really don't see the issue with this.

Regards,
- Graeme -

Michael Schnell wrote

And it does work with http://....

Here is some more information, but I haven't tested any of this because the GIT protocol works just fine for me.

http://www.emilsit.net/blog/archives/how-to-use-the-git-protocol-through-a-http-connect-proxy/

Regards,
- Graeme -

Of course it's a lot faster and much more stable than http. But if you are behind a firewall you are required to use http: (or ssh: via corkscrew).

I did a git clone via http: and it worked flawlessly and took less than an house.

So it seems to be not real problem-

-Michael