Development using git
This material is obsolete ...
This page describes git flows using email patch submissions, and should be updated with github based pull requests (Discuss)
Basic Git usage
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.
Using git config without --global let you configure other details for a specific git repository.
To be able send your commits (patches) via email you need configure an SMTP server.
For sending from a gmail address you can do:
Optionally, it is possible to skip the password prompt by adding it to the configuration with:
To reset CC mail attribute
[user] email = firstname.lastname@example.org name = Your Name [core] editor = nano pager = less -FXRS [sendemail] from = Your Name <email@example.com> smtpuser = firstname.lastname@example.org smtpserver = smtp.googlemail.com smtpencryption = tls smtpserverport = 587 suppresscc = self [push] default = simple
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.
If you want only the last 3 revisions:
Use the command below to see the full log of the trunk.
With write access
If you have write access to the Alpine the URL needs to be adjusted for cloning a repository
General GIT Workflow
- Make your file edits in your local checkout of the local copy of repository.
- Commit the changes in your local repository:
- Bring the rest of your local repository up to date:
- Check what you are going to push:
- Move your changes up to the master if you have write access create a patch if not. or