History of git

Version 30

git

All things git as it relates to bitweaver

Created by: spiderr, Last modification: 27 Feb 2013 (17:16 UTC) by spiderr
bitweaver is attempting to complete our CVS Migration to the git version control system. We have broken our CVS virtual modules in 150+ individual git repositories.

Gitting Started


Here are the steps to git up to speed and begin developing bitweaver on git:

1. Get some Git.

There are downloads for all major platforms however, be aware the anything other than the command line on linux is temperamental. Additional notes for using git with windows are being developed here.

2. Register on http://github.com

Let us know on ConnectingToIrc so we can add you as a collaborator. (BW Admins, there is a script to make this process simpler //WILL - PLEASE PUT SCRIPT SOMEPLACE ON MODELA//

3. Clone and Go

Since bitweaver is completely modular, the bitweaver.git clone master repository is simply a collection of submodules for each of the packages.

For standard read-only access, use:

git clone git://github.com/bitweaver/bitweaver.git -b READONLY

If you are a developer and need commit access, use:

git clone git@github.com:bitweaver/bitweaver.git -b DEV

This will create a 'bitweaver' directory where you are. Follow up with...

cd bitweaver
git submodule update --init
git submodule foreach --recursive git submodule update --init
git submodule foreach --recursive git checkout master

That will pull down all of the sub repositories for the directory structure the first clone created.
//style and icon sections need to be redirected to the correct subfolders//

Create your own bitweaver distro

If you have a custom set of modules, you can create your own master project. Here are the instructions:

mkdir newproject
cd newproject
# add the core set of packages for a minimal bitweaver install
for PACKAGE in kernel languages liberty storage themes users util wiki install; do git submodule add git@github.com:bitweaver/$PACKAGE.git; done
# initialize all nested submodules (mostly in util)
git submodule foreach --recursive git submodule update --init
# Create a root level index.php , copy from https://github.com/bitweaver/bitweaver/blob/master/index.php
vi index.php
# setup your own local config package, which typically is included in your master project git repo
mkdir config config/kernel/ config/themes config/icons
# Create a config bit_setup_inc.php , copy from https://github.com/bitweaver/config/blob/master/bit_setup_inc.php
vi config/bit_setup_inc.php
git add config index.php
# add some icons and themes
git submodule add git@github.com:bitweaver/iconset_tango.git config/icons/tango
git submodule add git@github.com:bitweaver/theme_basic.git config/themes/basic


Creating a new Repository

Contact a bitweaver admin to create a new repo on github for you.

Repository Locations


Github

http://github.com/bitweaver/
We are going to attempt to keep our code on github. There are is one major problem with Github currently - the lack of decent IRC notification.

bitweaver.org

We have a backup plan if github does not work out. We have our own install running gitosis, which was set up by /nickpalmer
git://git.bitweaver.org/
Contact an admin via ConnectingToIrc about getting a public key added. If github continues to suck, we will revert to bitweaver.org which is running gitosis, and we can mirror push'es to github on an update hook.

Import concepts in Git


Submodules

This is the second major stumbling block. Git submodules are similar to virtual modules in CVS. The achilles heal of git submodules is a "git submodule add ..." is tied to a particular commit for the submodule repository.

A lesser issue, submodules can only have directories in the current directory, so you have to nest. We cannot do the all-in-one "cvs co bitewaver" like we used to.

Stashing

http://progit.org/book/ch6-3.html

Reference Materials

http://gitref.org/
Page History
Date/CommentUserIPVersion
18 Jan 2014 (04:30 UTC)
spiderr75.182.99.22437
Current • Source
spiderr24.106.202.12336
View • Compare • Difference • Source
spiderr99.127.242.2535
View • Compare • Difference • Source
spiderr24.106.202.12334
View • Compare • Difference • Source
spiderr24.106.202.12333
View • Compare • Difference • Source
spiderr24.106.202.12332
View • Compare • Difference • Source
spiderr99.127.242.2531
View • Compare • Difference • Source
spiderr99.127.242.2530
View • Compare • Difference • Source
spiderr24.171.168.13029
View • Compare • Difference • Source
spiderr24.171.168.13026
View • Compare • Difference • Source
spiderr174.97.129.25521
View • Compare • Difference • Source
spiderr174.97.129.25520
View • Compare • Difference • Source
spiderr174.97.129.25519
View • Compare • Difference • Source
spiderr70.154.110.15718
View • Compare • Difference • Source
spiderr24.171.168.22117
View • Compare • Difference • Source
spiderr72.155.33.2916
View • Compare • Difference • Source
spiderr72.155.33.2915
View • Compare • Difference • Source
spiderr72.155.33.2914
View • Compare • Difference • Source
spiderr72.155.33.2912
View • Compare • Difference • Source
Lester Caine81.138.11.13610
View • Compare • Difference • Source
Lester Caine81.138.11.1369
View • Compare • Difference • Source
spiderr71.70.210.918
View • Compare • Difference • Source
spiderr71.70.210.917
View • Compare • Difference • Source
spiderr71.70.210.916
View • Compare • Difference • Source
spiderr71.70.210.915
View • Compare • Difference • Source
spiderr71.70.210.914
View • Compare • Difference • Source