Thanks Ales! Going through and check bit by bit!
Ales Hvezda wrote: > [snip] >> Yes, thanks Dan. I'm just started with the transition so, please >> no more CVS commits. I've dedicated today to getting this done, so please >> stand by. > > Okay, I think I am done. gerbv now joins gaf and pcb on the gpleda.org > server. I have done the following: > > * Create the following git repositories: > > http://git.gpleda.org/?p=gerbv.git;a=summary (gerbv src > code) > http://git.gpleda.org/?p=gerbvhtdocs.git;a=summary (website) > http://git.gpleda.org/?p=gerbv-tinyscheme.git;a=summary (tinyscheme-orig) Looking good! The tinyscheme repository was actually not necessary. But now it is there and wont hurt anyone. > * I have setup and populated: http://gerbv.gpleda.org (with one test > commit to fix some broken links and get the live website created). Haven't checked every its bitsy detail, but...looking good! > * Setup write permissions to all existing gerbv developers who have git > accounts on gpleda.org. > > If you have an git account gpleda.org, you can get a write-capable clone > of the git repositories by executing: > > git clone ssh://git.gpleda.org/home/git/gerbv.git > git clone ssh://git.gpleda.org/home/git/gerbvhtdocs.git > git clone ssh://git.gpleda.org/home/git/gerbv-tinyscheme.git Waiting for approval of my pub key. > For those people who do not have write access, you can clone of the > git repositories by executing: > > git clone git://git.gpleda.org/gerbv.git > git clone git://git.gpleda.org/gerbvhtdocs.git > git clone git://git.gpleda.org/gerbv-tinyscheme.git Actually not so good. $ git clone git://git.gpleda.org/gerbv.git Initialized empty Git repository in /home/spe/projects/gerbv/.git/ fatal: The remote end hung up unexpectedly > I have not tried commiting to the gerbv.git and gerbv-tinyscheme.git > repositories, so let me know if anybody runs into any errors. > > *** GETTING WRITE ACCESS **** > If you are a gerbv developer and you want write access, you need to send > me ([email protected]) a preferred username and the public part > (id_rsa.pub) of a ssh key (preferably with a passphrase set). > *** GETTING WRITE ACCESS **** > > Questions: > > * If somebody could disable cvs commits on sourceforge and put in a > redirect for the homepage on sourceforge, that would be great! Done! Just changing a line in Dans script. Even I can figure that out. > * What are the posting address for the gerbv commit mailing lists? [email protected] > * Could somebody please manually subscribe "[email protected]" to the > gerbv commit list with nomail, not metoo, nodups, and plain checked > on. I would do it myself except 1) I don't think I have admin rights > to the mailing lists and 2) gpleda.org does not receive any e-mail > (for verification purposes). I have subscribed according to your request. Why is this? > * The webpage needs some updating with regard to checking stuff out of the > repository, does anybody object if I do some updating? I see if I can fix as soon as my ssh key gets approved. > Please post if you see something wrong and I'll see if I can fix it. I couldn't clone out even as a plain user using git protocol (see above). > Thanks, Thank you Ales! If you ever pass by Stockholm I owe you a lot of beers. ;) Regards, /Stefan ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Gerbv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gerbv-devel
