World: r3wp

worked

lovely

now how old is your freebsd :) ?

based on your ubuntu, it's probably 5.4 :) ?

So, that clone gave me a full local repository, right? So, I can 
mess around with it... to get to know it?

Exactly!

No, I can't get away with that on freebsd. I think it's newer.

Probably updated it about 2 months ago.

I'd really suggest updating your Ubuntu at least to the previous 
LTS (8.04).

But that's another story :)

Yes, we use 8.xx on our servers.

So, what are git templates?

Huh?

git init --template=... ?

git gives me a warning that templates are not found in my git-core 
dir

perhaps because I did not install it, just running it local to my 
acct

yeah, that's most likely the case.

not proper env

I thought that this thing is going to be easy? :-)

In linux, as long as you don't need to recompile the kernel, it is 
considered easy.

Actually, that's prob considered easy too... since Linuxers do it 
for breakfast.

Anyway, I've got something to try out now on Linux, which is good. 
 For systems that might never run git, perhaps Andreas knows how 
to use git to auto-build gzips that we can have posted on the github.

No need to.

Github automatically builds tarballs and zipballs for you.

Great! Makes it easy.

:)

For example:
http://github.com/rebolsource/r3-hostkit/tarball/master

Instead of the final /master you can specify any tagname, branchname, 
or even revision name.

Very useful.

Ok, so I've read through gittutorial(7) ... and tried out various 
commands here... seems reasonable.

Encouraging!

What would be nice is to boil that tutorial down to just the 1, 2, 
3 steps that most R3 developers would need to know.

Agreed.

Be sure to include the right settings to choose for the Windows installer.

So, for github, would each developer have their own repository on 
that site?

Would be a possibility, yes.

Attaching patches to curecode issues is another.

Brian, any other setting besides the CRLF that you remember?

Also, how is that set on Linux? Not sure.

Linux does the sane thing per default :)

So... what's the general flow. For example:

1. developer clones host-kit repo
2. makes changes as needed
3. commits to local repo


Then, developer must somehow put them somewhere that we can pull 
from, correct?

Yes.

So, there's no "push" is there?

4a1. developer exports commits as patches
4a2. developer attaches the patches to a curecode issue

Do the CRLF-local, LF-repo on Windows; LF local and repo on Linux. 
Then line endings will be normalized. Only applies to text files 
of course.

4b1. developer forks the r3-hostkit repo on github to his github 
user account
4b1. developer pushes his changes to his github fork

4b3. developer notifies upstream via r3 chat, altme, curecode, or 
even github pull requests.

So, there's a git patch command to emit patch file?

Or does user do that manually?

git diff emits patches