Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!

Difference between revisions of "GitPhraseBook"

From Openembedded.org
Jump to: navigation, search
(add instructions for working with additional remote repositories)
m (Example 3: Working with a private branch)
 
(47 intermediate revisions by 18 users not shown)
Line 9: Line 9:
 
* [http://git.or.cz/gitwiki/GitDocumentation Official Documentation]
 
* [http://git.or.cz/gitwiki/GitDocumentation Official Documentation]
 
* [http://git.or.cz/gitwiki/GitCheatSheet Cheat Sheet]
 
* [http://git.or.cz/gitwiki/GitCheatSheet Cheat Sheet]
 +
* [http://book.git-scm.com/ The Git Community Book]
 
* [http://eagain.net/articles/git-for-computer-scientists/ Git For Computer Scientists]
 
* [http://eagain.net/articles/git-for-computer-scientists/ Git For Computer Scientists]
 +
* [http://progit.org/book/ Pro Git]
 
* [http://www.google.com/search?q=git+documentation&ie=utf-8&oe=utf-8&aq=t Google Search]
 
* [http://www.google.com/search?q=git+documentation&ie=utf-8&oe=utf-8&aq=t Google Search]
  
Line 16: Line 18:
  
 
=== Getting the data (read-only) ===
 
=== Getting the data (read-only) ===
   git clone git://git.openembedded.net/openembedded
+
   git clone git://git.openembedded.org/openembedded
  
 
=== Getting the data (write-access) ===
 
=== Getting the data (write-access) ===
Line 22: Line 24:
 
For this command to succeed you need to have provided a SSH key (see [[#Generating a ssh key]]).
 
For this command to succeed you need to have provided a SSH key (see [[#Generating a ssh key]]).
  
   git clone git@git.openembedded.net:openembedded
+
   git clone git@git.openembedded.org:openembedded
  
 
=== Generating a ssh key ===
 
=== Generating a ssh key ===
Line 34: Line 36:
  
 
This command will fetch new objects from the server, and try to put your local changes on top of the newly fetched revisions for your current branch. If you have no local revisions you will still be updated.
 
This command will fetch new objects from the server, and try to put your local changes on top of the newly fetched revisions for your current branch. If you have no local revisions you will still be updated.
 +
 +
Depending on your git version this command may fail and does not report any error message: Version 1.5.6.5 (Debian Lenny) does, 1.5.5.1 (Fedora 9) does not. The message is
 +
"refusing to pull with rebase: your working tree is not up-to-date".
 +
 +
In case that 'git pull --rebase' does not work for you, try the following:
 +
 +
  git stash
 +
  git pull --rebase
 +
  git stash pop
 +
 +
This information was taken from the [http://wiki.videolan.org/Git#Setting_up_.22git_up.22_.28Tip.29 VideoLAN Wiki].
  
 
=== Checking out a branch ===
 
=== Checking out a branch ===
Line 46: Line 59:
  
 
=== Configuring your tree for commits ===
 
=== Configuring your tree for commits ===
 +
 +
If you forget this, your name and email in the commit mails, may be messed up.
 +
 
   git config user.name "Your Name"
 
   git config user.name "Your Name"
   git config user.mail "you@name"
+
   git config user.email "you@name"
  
 
== Doing things with git ==
 
== Doing things with git ==
Line 70: Line 86:
 
   git add -i
 
   git add -i
 
   git commit
 
   git commit
 +
 +
=== Automatically add 'Signed-off-by:' statement ===
 +
  git commit -s
  
 
=== Amending to your changes ===
 
=== Amending to your changes ===
Line 79: Line 98:
 
== Commiting someones else work ==
 
== Commiting someones else work ==
 
   git commit --author "Other One <other@one>"
 
   git commit --author "Other One <other@one>"
 +
 +
== Create patches suitable for the mailing list  ==
 +
This creates a series of patches of all your added work
 +
  git format-patch origin
 +
You can add a 'Signed-off-by:' statement by
 +
  git format-patch -s origin
 +
 +
== Create series of patches suitable for the mailing list  ==
 +
Include the last 17 commits.
 +
 +
The patches will have a header [PATCH n/17]
 +
  git format-patch -n -17
 +
 +
== Create version 2 of a patch after feedback from the mailing list  ==
 +
  git format-patch -n -17 --subject-prefix='PATCH v2'
 +
 +
== Send email to mailing list ==
 +
  git send-email <patch-list>
  
 
== Pushing your changes ==
 
== Pushing your changes ==
 
   # just pushes the org.openembedded.dev
 
   # just pushes the org.openembedded.dev
 
   git push origin org.openembedded.dev
 
   git push origin org.openembedded.dev
 +
 +
  # the same, just simpler
 +
  git push
  
 
   # just pushes your things to a test branch. Use the right branch! dangerous!
 
   # just pushes your things to a test branch. Use the right branch! dangerous!
   git push origin org.openembedded.dev:yourname/testbranch
+
   git push origin yourname/testbranch
  
 
   # delete a branch
 
   # delete a branch
Line 112: Line 152:
 
==== Delete your branch after it was merged ====
 
==== Delete your branch after it was merged ====
 
   git push origin :yourname/yourfeature
 
   git push origin :yourname/yourfeature
 +
 +
==== Prune remote branches which have been deleted ====
 +
  git remote prune origin
  
 
==== Upgrade/Rebase your branch to the latest version ====
 
==== Upgrade/Rebase your branch to the latest version ====
Line 151: Line 194:
 
   git fetch
 
   git fetch
  
   # show you local branches and which branch you are in
+
   # show your local branches and which branch you are in
 
   git branch
 
   git branch
  
   # show you all branches
+
   # show all branches
 
   git branch -a
 
   git branch -a
  
Line 169: Line 212:
 
   # Kill the last commit
 
   # Kill the last commit
 
   git reset HEAD^1
 
   git reset HEAD^1
 +
 +
  # Prepare a set of patch
 +
  git format-patch origin
 +
 +
  # What changes have I made
 +
  git status
 +
 +
  # List details of those changes
 +
  git diff --cached
  
 
== Working with additional git repositories ==
 
== Working with additional git repositories ==
Line 216: Line 268:
  
 
  gtk+ 2.8.4: add patch for buffer overflow
 
  gtk+ 2.8.4: add patch for buffer overflow
 +
 +
=== Example 3: Working with a private branch ===
 +
 +
Download and create a remote private branch "origin/ulf/linux-2.6.39-2011-11-22".
 +
The local copy of the branch will be called "ulf/linux-2.6.39-2011-11-22".
 +
When you do:
 +
 +
git branch -a
 +
 +
local branches will be at the top, and remote branches
 +
will be sorted in alpabetical order.
 +
 +
Create the local branch and prepare:
 +
 +
git clone git@git.openembedded.org:openembedded
 +
cd openembedded
 +
git config user.name "Ulf Samuelsson"
 +
git config user.email "ulf_samuelsson@telia.com"
 +
git checkout -b ulf/linux-2.6.39-2011-11-22 origin/org.openembedded.dev
 +
 +
Add something:
 +
 +
touch test
 +
git add test
 +
git commit -m "test" test
 +
 +
Create a remote private branch from the local branch.
 +
It will be called "origin/ulf/linux-2.6.39-2011-11-22"
 +
 +
git push origin ulf/linux-2.6.39-2011-11-22
 +
 +
Create a local branch, based on your remote private branch:
 +
 +
git checkout -b ulf/linux-2.6.39-2011-11-22 origin/ulf/linux-2.6.39-2011-11-22
 +
 +
Add something to your local branch:
 +
 +
touch test2
 +
git add test2
 +
git commit -m "test2" test2
 +
 +
Update your remote private branch:
 +
 +
git push origin ulf/linux-2.6.39-2011-11-22
 +
 +
Once the remote branch has been updated from a local
 +
branch you need to update any other local branches by:
 +
 +
git fetch origin
 +
 +
Prepare patches for the mailing list:
 +
 +
git format-patch origin
 +
 +
Remove your local branch:
 +
 +
git checkout origin/org.openembedded.dev
 +
git branch -d ulf/llinux-2.6.39-2011-11-22
 +
 +
or possibly:
 +
 +
git branch -D ulf/linux-2.6.39-2011-11-22
 +
 +
Note that the openembedded git server will not
 +
allow you to delete a private branch at this time.
 +
Send an email to the mailing list and this will be fixed.
  
 
[[Category:Dev]]
 
[[Category:Dev]]
 
[[Category:User]]
 
[[Category:User]]

Latest revision as of 20:42, 22 November 2011

Contents

[edit] Git Phrase Book

NOTE: For increased pleasure use git 1.5 or later.

[edit] Pointers

There are plenty of good git tutorials on the net. A small collection of links can be seen below:

[edit] Setup

[edit] Getting the data (read-only)

 git clone git://git.openembedded.org/openembedded

[edit] Getting the data (write-access)

For this command to succeed you need to have provided a SSH key (see #Generating a ssh key).

 git clone git@git.openembedded.org:openembedded

[edit] Generating a ssh key

To be able to push to the OpenEmbedded git server you will need to have the right permissions. This starts with having your public ssh key on the server. Generate a key and send the public key to the one of the core developers.

 # send the resulting pub key to koen, mickeyl, RP, or zecke [email address]
 ssh-keygen -t rsa or -t dsa

[edit] Upgrading your data (lurking)

 git pull --rebase

This command will fetch new objects from the server, and try to put your local changes on top of the newly fetched revisions for your current branch. If you have no local revisions you will still be updated.

Depending on your git version this command may fail and does not report any error message: Version 1.5.6.5 (Debian Lenny) does, 1.5.5.1 (Fedora 9) does not. The message is "refusing to pull with rebase: your working tree is not up-to-date".

In case that 'git pull --rebase' does not work for you, try the following:

 git stash
 git pull --rebase
 git stash pop

This information was taken from the VideoLAN Wiki.

[edit] Checking out a branch

 # See which branches are available
 git branch -a
 # In theory create a branch and switch
 git checkout -b local origin/remote
 # you will now be in the dreambox branch and track this.
 git checkout -b org.openembedded.dreambox origin/org.openembedded.dreambox

[edit] Configuring your tree for commits

If you forget this, your name and email in the commit mails, may be messed up.

 git config user.name "Your Name"
 git config user.email "you@name"

[edit] Doing things with git

[edit] Commit Message

<package name> <version>| <package category> | <configfile/class name>: <summary> 
{  - <detail 1>
   - <detail 2>}*

[edit] Making your changes (old way)

 # if you have new files
 git add your/new/file
 # Commit everything
 git commit -a

[edit] Making your changes (better way)

 git add your/changed/files
 git commit

[edit] Making your changes (a cool way)

 git add -i
 git commit

[edit] Automatically add 'Signed-off-by:' statement

 git commit -s

[edit] Amending to your changes

You forgot something, no big deal, change the commit

 git add your/others/changes
 git commit --amend

[edit] Commiting someones else work

 git commit --author "Other One <other@one>"

[edit] Create patches suitable for the mailing list

This creates a series of patches of all your added work

 git format-patch origin

You can add a 'Signed-off-by:' statement by

 git format-patch -s origin

[edit] Create series of patches suitable for the mailing list

Include the last 17 commits.

The patches will have a header [PATCH n/17]

 git format-patch -n -17

[edit] Create version 2 of a patch after feedback from the mailing list

 git format-patch -n -17 --subject-prefix='PATCH v2'

[edit] Send email to mailing list

 git send-email <patch-list>

[edit] Pushing your changes

 # just pushes the org.openembedded.dev
 git push origin org.openembedded.dev
 # the same, just simpler
 git push
 # just pushes your things to a test branch. Use the right branch! dangerous!
 git push origin yourname/testbranch
 # delete a branch
 git push origin :yourname/testbranch

[edit] Dealing with conflicts

Git will tell you what needs resolving. You can use kdiff3, meld, or many other tools to resolve the conflict. Don't be afraid you can easily redo and undo everything.

 # Conflicts from here or something else
 git pull --rebase
 git status
 # Starts interactive resolver, TOOL can be kdiff3, meld or anything else
 git mergetool --tool=TOOL filename
 git rebase --continue or similar once everything got resolved

[edit] Working with git

[edit] Feature branches

[edit] Create your own short lived feature branch

 git checkout -b yourname/yourfeature origin/org.openembedded.dev

[edit] Push your feature branch

 git push origin yourname/yourfeature

[edit] Delete your branch after it was merged

 git push origin :yourname/yourfeature

[edit] Prune remote branches which have been deleted

 git remote prune origin

[edit] Upgrade/Rebase your branch to the latest version

 git fetch origin
 git rebase origin/org.openembedded.dev

[edit] Change your history

 # select edit, squash, pick to say what to do with the commit
 git rebase -i origin/org.openembedded.dev
 # to abort the operation on a tricky merge
 git rebase --abort
 # to find out a previous state to use with git reset
 git reflog

[edit] Seeing changes

[edit] Log

 # See what happened in a branch
 git log branch
 # See the change, HEAD or branch name will work too
 git show --color (COMMIT)
 #  Only show you change on foo/file
 git show --color HEAD -- foo/file
 # Graphical browser
 gitk

[edit] What did you change

 # Lists you the revs that are only in your branch compared to org.openembedded.dev
 git rev-list origin/org.openembedded.dev..

[edit] Other Interesting commands

 # fetch new revisions from all remote repositories
 git fetch
 # show your local branches and which branch you are in
 git branch
 # show all branches
 git branch -a
 # create a branch and switch to it
 git checkout -b MYNAME origin/THEIRNAME
 # upgrade a branch
 git push origin org.openembedded.dev
 git reflog
 # Change your index to be at the state of REF
 git reset REF
 # Kill the last commit
 git reset HEAD^1
 # Prepare a set of patch
 git format-patch origin
 # What changes have I made
 git status
 # List details of those changes
 git diff --cached

[edit] Working with additional git repositories

One of the neat things with git is you can easily work with external repositories.

 # add an external repository:
 git remote add openmoko.org git://git.openmoko.org/git/openmoko.git
 git fetch openmoko.org
 
 # view all remote branches available
 git branch -r
 # view changes on a remote branch
 gitk openmoko.org/org.openmoko.asu.stable
 git log openmoko.org/org.openmoko.asu.stable
 # view all diffs
 git diff origin/org.openembedded.dev openmoko.org/org.openmoko.asu.stable
 
 # view diffs in just one subdirectory
 git diff origin/org.openembedded.dev openmoko.org/org.openmoko.asu.stable classes


[edit] Examples

[edit] Example 1:

 vi packages/gaim/gaim.inc
 git commit packages/gaim/gaim.inc
 git pull --rebase

should have a log message like this:

gaim: make sure do_install does its job in gaim.inc
* install lib to ${libdir} instead of /usr/lib
* remove executable bits from docs

[edit] Example 2:

diff /tmp/foo.c /oe/work/gtk+-2.8.4-r0/gtk+-2.8.4/src/foo.c > gtk-2.8.4/fix-foo.patch
vi gtk+_2.8.4.bb
git add gtk-2.8.4/fix-foo.patch
git commit gtk-2.8.4/fix-foo.patch gtk+_2.8.4.bb
git pull --rebase

should have a log message like this:

gtk+ 2.8.4: add patch for buffer overflow

[edit] Example 3: Working with a private branch

Download and create a remote private branch "origin/ulf/linux-2.6.39-2011-11-22". The local copy of the branch will be called "ulf/linux-2.6.39-2011-11-22". When you do:

git branch -a

local branches will be at the top, and remote branches will be sorted in alpabetical order.

Create the local branch and prepare:

git clone git@git.openembedded.org:openembedded
cd openembedded
git config user.name "Ulf Samuelsson"
git config user.email "ulf_samuelsson@telia.com"
git checkout -b ulf/linux-2.6.39-2011-11-22 origin/org.openembedded.dev

Add something:

touch test
git add test
git commit -m "test" test

Create a remote private branch from the local branch. It will be called "origin/ulf/linux-2.6.39-2011-11-22"

git push origin ulf/linux-2.6.39-2011-11-22

Create a local branch, based on your remote private branch:

git checkout -b ulf/linux-2.6.39-2011-11-22 origin/ulf/linux-2.6.39-2011-11-22

Add something to your local branch:

touch test2
git add test2
git commit -m "test2" test2

Update your remote private branch:

git push origin ulf/linux-2.6.39-2011-11-22

Once the remote branch has been updated from a local branch you need to update any other local branches by:

git fetch origin

Prepare patches for the mailing list:

git format-patch origin

Remove your local branch:

git checkout origin/org.openembedded.dev
git branch -d ulf/llinux-2.6.39-2011-11-22

or possibly:

git branch -D ulf/linux-2.6.39-2011-11-22

Note that the openembedded git server will not allow you to delete a private branch at this time. Send an email to the mailing list and this will be fixed.

Personal tools
Namespaces

Variants
Actions
Navigation
Categories
OE services
Toolbox