Git

This material is obsolete ... This page describes git flows using email patch submissions, and should be updated with github based pull requests (Discuss)

This document describes how to use git for Alpine Linux development and related projects. If you just want to browse the Alpine git repositories, please visit git.alpinelinux.org.

Configure your global git config

First you need to tell your name and email to git. This name and email will show up in all your commits.

git config --global user.name "Your Name Comes Here" git config --global user.email you@yourdomain.example.com

Using git config without --global let you configure other details for a specific git repository.

Tip: If you want to use git with colored output use:

git config --global color.ui true git config --global core.pager more

Tip: If you want to use git with proxy server:

git config --global http.proxy http://proxy_ip:proxy_port

Cloning a repository via Git

There are two ways to work with the Alpine git repository...

• ...without write access.
• ...with write access.

git.alpinelinux.org shows all available Alpine git repositories.

Without write access

If you want to clone the Alpine aports repository, switch to the directory you want to have the aports/ directory in and launch git.

git clone git://git.alpinelinux.org/aports.git

Tip: If you are using proxy server:

git clone http://git.alpinelinux.org/cgit/aports

If you want only the last 3 revisions:

git clone git://git.alpinelinux.org/aports.git --depth 3

Use the command below to see the full log of the trunk.

git log

With write access

If you have write access to the Alpine the URL needs to be adjusted for cloning a repository

git clone ssh://username@git.alpinelinux.org/aports.git

General GIT Workflow

1. Make your file edits in your local checkout of the local copy of repository.
2. Commit the changes in your local repository:

   git commit

3. Bring the rest of your local repository up to date:

   git pull --rebase

4. Check what you are going to push:

   git log origin..master

5. Move your changes up to the master if you have write access

   git push

   or create a patch if not.

Other related articles

• Basic usage
• Package Maintainers
• Creating patches
• Developer repositories
• Using Cgit

Further reading

• Git Tutorial
• Git - SVN Crash Course (quickstart if you know svn)
• A tour of git: the basics Recommended
• The Git Community Book
• Git From the Bottom Up
• Very good Git guide