World: r3wp

Brian, the only trouble with letting git do the line ending normalisation 
is that it is a bit troublesome. It's generally easier to just have 
git not touch the line endings at all and use a properly set-up editor 
instead.

Oh, I was used to Hg just doing that without the problems. Can we 
reject submissions that don't have the right line endings?

Yes.

And I assume every major C/C++ compiler on Windows can handle LF-endings 
with no complaint.

We only have to support one that does.

Is there a pending proposal to fix git's line ending munging so it 
works properly, like Hg's?

(-> "Source control")

Useful git guide: www.sourcemage.org/Git_Guide

Shows examples of many commands. In FAQ format.

A few examples there are a bit out of date, though.

For example, git-update-index is no longer needed to resolve merge 
conflics. You'd use git-add instead.

And in the "advanced usage" examples, a few commands have been simplified.

A question: for new releases, should I push to my carls repo, the 
rebol sandbox, or r3-hostkit ?

Asked another way: how does r3-hostkit get updated?

Do we always pull into it?

I would push into rebol/r3-hostkit for now.

(Which does not yet exist.)

The rebol/sandbox is just if you want to play around a bit with Github.

We'll probably just delete that afterwards.

Of course you can also create a repo under your carls user for playing 
around.

Another question: do you normally access github from git? Do you 
ever use the web interface?

You hardly need to use the web interface.

Good to know.

Is there a command for renaming files?

git-mv

If I remove a file from my repo, then I push . does it remove it 
from the target repo?

If you remove with git-rm, then create a commit with git-commit, 
then git-push: yes.

If you remove with something else, you'll still need to create a 
commit for that remove.

What is the reason to use git-push vs git push ?

(and other cmds)

That's just a convetion I use to refer to commands.

When I say git-push, you actually writ e `git push`.

But if you want to know more: man git-push

Well, I must say... I am impressed so far. There are a lot of "nice 
touches"

I'm sure you'll be even more impressed when you dig deeper.

It is so _extremely_ simple at it's core :)

Yes, and I want to make sure that the R3 Git Guide that we'll post 
shows that this is very simple to do.

I think many people have gone to use SVN and will resist a bit using 
something new.

Of course, in the worst cases, they can just use the zip/gz file 
downloads for read access.

Or they can even use svn for read access :)

Try it:
svn co https://svn.github.com/rebolsource/r3-hostkit.git

On the other hand, I've never met anyone who went back after giving 
a modern DVCS (which means mostly Git and Hg) a serious try.

So, to mark an official release, like A110, is it only necessary 
to commit with that message, or do we need to make a tag as well?

I would suggest adding a tag as well.

A tag is a minimal object in git, just pointing to a commit.

They are cheap! :)

I'm running out of questions. (A good thing.)

Incorporating changes from others will raise some questions.

But I think we should not get ahead of ourselves.

Yes, we can deal with that as it happens.

Ok, so here's the rough plan...