World: r3wp

btw - can Tortoise SVN be used as a GIT client, or is that something 
different? I like how I upgraded RebGUI - what was the system RebGUI 
used based upon?

There is TortoiseGIT: http://code.google.com/p/tortoisegit/

Henrik, you could start by putting the R3-GUI into Git!

I'll see if there is anyone interested in exporting it, but I'm afraid 
the source would be constantly out of sync with what we have in RM 
Asset's repository.

what does Robert use?

... but you would not have to constantly announce it - it could save 
you a bit of work, no?

Pekr, that's simply a snapshot, which takes a minute to do, thanks 
to our build system.

GrahamC, RM Asset uses SVN.

there's likely an automatic tool to export from SVN to git

distributed source controls are much more flexible and easy to use 
than centralized ones like svn.

there is no concept I have to put it *the* repository.

its easier to do a grid of different setups. not just a linear sequence 
of versions.

I haven't yet seen a good argument that Git is better (than Hg, at 
least)

 - Brian... so... people who have used both for years can be just 
 ignored I guess.


Just read how they work, if it's not obvious why GIT is better, then 
I don't know what to say.

I don't have experience with Git(only used Hg) and I have nothing 
against learning and using it. The only thing I hate about it so 
far is the lost 1GB!! of diskspace after installing TortoiseGit for 
Windows :)

holy cow ... 1GB !

I mean... didn't I use an OS that fit on a 512kb rom just 10 years 
ago... seems like a lifetime ago.

well, that's all the msys stuff that is needed to run the git, unfortunately

this aproach is like 'hey, you need the whole OS for my app, I don't 
care what you are using"

The idea of GIT might be good, but where do we end up, if we suddenly 
rely on 3-5 different systems that require a 10GB installation of 
all sorts of unmanagable components?

once we have ssh on r3 (in whatever form) I think we should be able 
to build the entire git toolset with REBOL at a fraction of msys 
stuff.  I already did a complete source control system (though with 
a completely different model) called distro-bot and its hardly 1GB!

rebol in and of itself already does most of the low-level OS stuff... 
just two days ago... I used R2 as a delete function in order to polish 
a windows GCC script.  this strikes me as a similar situation where 
rebol could be used to probably replace a sizeable portion of the 
msys stuff... though it might not be as fast and optimised... that 
I do concede.

Why you would need 1GB for TortoiseGit? I installed this:

http://code.google.com/p/msysgit/downloads/detail?name=Git-1.7.3.1-preview20101002.exe&can=3&q=
and it seems to be enough.

I don't know why it was so big..I installed it half year ago, maye 
they fixed that. I guess your link is just some cli version? I want 
gui version.

Yes, msysgit is just a CLI

When looking at my pc I installed this in these days: msysGit-fullinstall-1.7.0.2-preview20100309.exe 
then installed Tortoise over it.

Then when I check size of c:\msysgit\ dir I got 1 307 758 191 bytes


I'll try to uninstall and use the latest version to see if it is 
better.

No, it has gui as well.

gitk and git-gui, yes.

tortoisegit just adds a kind of explore integration that many are 
already familiar with.

Another option for explorer integration would be Git Extensions:
http://code.google.com/p/gitextensions/

(And yes, even plain msysgit comes with minimal, optional explorer 
integration in the form of "launch a git shell here" and "launch 
git gui here", if I remember correctly.)

The installer from my link above adds the explorer extension as well.

Oldes, thanks for the link to the latest version. This seems to be 
better..'only' 180MB :-)

Quick notes:


I downloaded via the Git link that Oldes posted above. It's ~12MB 
(reasonable.)


Installed fine on XP.  Yes, this is a shell version, which is fine 
with me since I like to use scripts anyway for merges, builds, and 
releases.


I have yet to try git with github. It would be great if someone could 
post the magic command line to checkout  the existing repository 
(anonymous currently),


Regarding GUI version: it would not be difficult for someone to wrap 
a few REBOL calls it to give you a bit more GUI feel. Not perfect 
of course, but something clickable.

So, next steps for A110 in git are:


1. Obtain a user account on github. (with the permissions I need 
from Andreas.)


2. Commit new A110 sources to github. (probably an overwrite, not 
a merge)


3. Commit A110 libs to github. Binary, compressed, and version/platform-dependent.

4. Tag it all as A110 (however that's done in git).


Does this sound about right with you git gurus?  Let me know of any 
special steps, proceedures, so this can happen today.

I'm using Git second day, so I'm far to be called git guru, but I 
think that you could just obtain account without Andreas' permissions 
and commit the sources under your name.

Checklist created: Git Move -- steps for A110 git-based release

Andreas, feel free to update checklist with any additional things 
that you want to add.

Oldes, mostly. There was something he mentioned to me earlier.

To clone the current repository:
$ git clone git://github.com/rebolsource/r3-hostkit.git

Ok, so that's like a checkout?

http://eagain.net/articles/git-for-computer-scientists/

Yes, that's somewhat like a checkout.

Worked. Got it. Nice.

git move checklist updated

The general model is that if you plan on making changes to the codebase, 
you usually would "fork" (lowercase) the project on the GitHub site. 
 It is not typical for people to give write access to others on their 
repository.  So that URL ( git://github.com/rebolsource/r3-hostkit.git 
) is read-only.

Carl was referring to something else, I reserved the "rebol" username 
yesterday.

Carl, to "overwrite" your local stuff with the new sources, just 
remove everything but the .git/ directory.

Then copy over your changed sources and do a "git add -u .".

A "git diff --cache" will then show you the changes compared to the 
last commit.

Use "git commit" to commit those changes.