Difference between revisions of "Development/Tutorials/Git/Recipes"

Jump to: navigation, search
m (Text replace - "</code>" to "</syntaxhighlight>")
Line 7: Line 7:
  
 
When you issue:
 
When you issue:
<code>git branch -a</code>
+
<code>git branch -a</syntaxhighlight>
 
you get
 
you get
 
<code>
 
<code>
Line 23: Line 23:
 
   remotes/origin/kdepim/enterprise-4.1
 
   remotes/origin/kdepim/enterprise-4.1
 
   remotes/origin/master
 
   remotes/origin/master
</code>
+
</syntaxhighlight>
 
The red-colored lines are showing you the branches that are living into the main repository (you must have enabled git colors before this).  
 
The red-colored lines are showing you the branches that are living into the main repository (you must have enabled git colors before this).  
  
Line 30: Line 30:
 
<code>
 
<code>
 
git checkout -b KDE/4.6 origin/KDE/4.6
 
git checkout -b KDE/4.6 origin/KDE/4.6
</code>
+
</syntaxhighlight>
 
This will get get you on the backport branch. Verify the diff between this old branch and the origin branch where you commited your fix :
 
This will get get you on the backport branch. Verify the diff between this old branch and the origin branch where you commited your fix :
 
<code>
 
<code>
 
git diff origin <fileYouModified>
 
git diff origin <fileYouModified>
</code>
+
</syntaxhighlight>
  
 
To apply your fix, do this:
 
To apply your fix, do this:
 
<code>
 
<code>
 
git cherry-pick 0f601b3d28
 
git cherry-pick 0f601b3d28
</code>
+
</syntaxhighlight>
 
You just applied your fix (well, if you get merging errors, just fix them as usual). See it by yourself:
 
You just applied your fix (well, if you get merging errors, just fix them as usual). See it by yourself:
<code>git log</code>
+
<code>git log</syntaxhighlight>
  
 
Now push your changes:
 
Now push your changes:
 
<code>
 
<code>
 
git push
 
git push
</code>
+
</syntaxhighlight>
 
Don't forget to get back on the main branch:
 
Don't forget to get back on the main branch:
<code>git checkout master</code>
+
<code>git checkout master</syntaxhighlight>

Revision as of 19:41, 29 June 2011

noframe
 
Warning
This page is yet to be reviewed for changes required by the migration to Git. Information and commands on this page may no longer be valid and should be used with care. Please see the KDE Git hub page for more details.


GIT/KDE useful recipes

Backporting fixes

Let's say you just fixed a bug in kde-apps and you commited it to the master and git reported it as commit id 0f601b3d28. You want now to get it backported to the latest released version.

When you issue: git branch -a</syntaxhighlight> you get <code>

  • master
 remotes/origin/4.6
 remotes/origin/HEAD -> origin/master
 remotes/origin/KDE/4.0
 remotes/origin/KDE/4.1
 remotes/origin/KDE/4.2
 remotes/origin/KDE/4.3
 remotes/origin/KDE/4.4
 remotes/origin/KDE/4.5
 remotes/origin/KDE/4.6
 remotes/origin/kdepim/enterprise-4.0.83
 remotes/origin/kdepim/enterprise-4.1
 remotes/origin/master

</syntaxhighlight> The red-colored lines are showing you the branches that are living into the main repository (you must have enabled git colors before this).

You need to backport to the last released version, which lives in the remotes/origin/KDE/4.6:

<code> git checkout -b KDE/4.6 origin/KDE/4.6 </syntaxhighlight> This will get get you on the backport branch. Verify the diff between this old branch and the origin branch where you commited your fix : <code> git diff origin <fileYouModified> </syntaxhighlight>

To apply your fix, do this: <code> git cherry-pick 0f601b3d28 </syntaxhighlight> You just applied your fix (well, if you get merging errors, just fix them as usual). See it by yourself: <code>git log</syntaxhighlight>

Now push your changes: <code> git push </syntaxhighlight> Don't forget to get back on the main branch: <code>git checkout master</syntaxhighlight>


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal