Difference between revisions of "Pacman Development"

From ArchWiki
Jump to: navigation, search
(Initial Draft)
 
m (GIT Cheat Sheet: amend after a push is hazardous)
Line 33: Line 33:
 
   git format-patch master
 
   git format-patch master
  
Amend patch
+
Amend patch (Don't use it after a push)
 
   git commit -a --amend -s
 
   git commit -a --amend -s
  

Revision as of 04:17, 23 June 2008

Tango-document-new.pngThis article is a stub.Tango-document-new.png

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in Talk:Pacman Development#)

Interested in Pacman Development? This page should help you get started.

Remember that if you think something belongs on this page, add it! The current pacman developers are not likely to know what people need to know and should be on this page.

External References and Links

GIT Cheat Sheet

Clone git repo - only needed once

 git clone git://projects.archlinux.org/pacman.git pacman

Enable useful hooks

 chmod +x .git/hooks/{applypatch-msg,commit-msg,pre-commit,pre-rebase}

Create branch "<branch>"

 git branch <branch>

Work with branch "<branch>"

 git checkout <branch>

Commit changes on current branch and make patch to master branch

 git commit -a -s
 git format-patch master

Amend patch (Don't use it after a push)

 git commit -a --amend -s

Add file "<file>"

 git add <file>

Remove file "<file>"

 git rm <file>

Remove branch "<branch>"

 git branch -D <branch>

Update master branch

 git checkout master
 git pull

Merge changes on master with "<branch>"

 git rebase master <branch>

Get maint branch

 git branch -r
 git checkout -b maint origin/maint