<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for jcorbin_wunjo</title><link>http://disqus.com/by/jcorbin_wunjo/</link><description></description><atom:link href="http://disqus.com/jcorbin_wunjo/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 12 Feb 2009 13:12:15 -0000</lastBuildDate><item><title>Re: git ready &amp;raquo; pull with rebase</title><link>http://gitready.com/advanced/2009/02/11/pull-with-rebase.html#comment-6211318</link><description>&lt;p&gt;I'd like to add on to that "awesome tip",   tracking branches are usually what you want by default.&lt;/p&gt;&lt;p&gt;More precisely: you'll know it if you don't want to track in my experience... soo:&lt;/p&gt;&lt;p&gt;% git config --global branch.autosetupmerge true&lt;/p&gt;&lt;p&gt;Is usually great that way when you say something like:&lt;br&gt;% git checkout -b &amp;lt;bla&amp;gt; &amp;lt;remote&amp;gt;/&amp;lt;bla&amp;gt;&lt;/p&gt;&lt;p&gt;Things work about as naturally as you'd expect.&lt;/p&gt;&lt;p&gt;--no-track is easy enough to add in the fewer cases where you don't want this behavior than it is to remember to always --track in git-checkout or git-branch.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jcorbin_wunjo</dc:creator><pubDate>Thu, 12 Feb 2009 13:12:15 -0000</pubDate></item><item><title>Re: git ready &amp;raquo; status in your prompt</title><link>http://gitready.com/2009/01/23/status-in-your-prompt.html#comment-5603716</link><description>&lt;p&gt;If you use zsh, you may be interested in my &lt;a href="http://www.wunjo.org/zsh-git" rel="nofollow noopener" target="_blank" title="http://www.wunjo.org/zsh-git"&gt;http://www.wunjo.org/zsh-git&lt;/a&gt; .&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jcorbin_wunjo</dc:creator><pubDate>Tue, 27 Jan 2009 18:10:28 -0000</pubDate></item><item><title>Re: git ready &amp;raquo; ignoring files</title><link>https://disqus.com/home/discussion/git-ready/git_ready_raquo_ignoring_files_40/#comment-5477386</link><description>&lt;p&gt;@glennfu&lt;/p&gt;&lt;p&gt;Instead of using ignores or unstaging changes at all, you'd be better off using a local branch, and developing in topic branchs. Example workflow like:&lt;/p&gt;&lt;p&gt;% git checkout --track -b local master&lt;br&gt;% git config branch.local.rebase true # the branch should always rebase on pull&lt;br&gt;% &amp;lt; tweak environment and commit in local&amp;gt;&lt;/p&gt;&lt;p&gt;Now let's say that for good form you keep topic branches well maintained, so:&lt;br&gt;% git checkout --track -b topic local&lt;br&gt;% git config branch.topic.rebase true # see man git-config to automate this and the --track above&lt;br&gt;% &amp;lt;work on="" topic,="" make="" some="" commits=""&amp;gt;&lt;/p&gt;&lt;p&gt;So now you have this branch topic, that's based on your local change branch, and you want to merge changes back into master to push them up to some remote (f.e. your private publication repo  that others pull from, or in the case of git-svn merge things into master to dcommit).&lt;/p&gt;&lt;p&gt;% git rebase --onto master local work&lt;br&gt;% git checkout master&lt;br&gt;% git merge work&lt;br&gt;% git branch -d work&lt;/p&gt;&lt;p&gt;Now the only thing left other than sending changes in master back upstream is to bring your local branch up to speed:&lt;br&gt;% git checkout local&lt;br&gt;% git pull # implies a rebase on head, see above&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jcorbin_wunjo</dc:creator><pubDate>Thu, 22 Jan 2009 16:27:46 -0000</pubDate></item></channel></rss>