<?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 BartTrojanowski</title><link>http://disqus.com/by/BartTrojanowski/</link><description></description><atom:link href="http://disqus.com/BartTrojanowski/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 16 Apr 2009 14:57:58 -0000</lastBuildDate><item><title>Re: git ready &amp;raquo; find unmerged commits</title><link>http://gitready.com/intermediate/2009/04/16/find-unmerged-commits.html#comment-8269007</link><description>&lt;p&gt;I find that a nice replacement for git-cherry is&lt;/p&gt;&lt;p&gt;  git log --cherry-pick other-branch...&lt;/p&gt;&lt;p&gt;which tells you what patches are there and not here.  Note the 3-dots, not two (see description in man git-rev-list).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BartTrojanowski</dc:creator><pubDate>Thu, 16 Apr 2009 14:57:58 -0000</pubDate></item><item><title>Re: git ready &amp;raquo; smartly save stashes</title><link>http://gitready.com/beginner/2009/03/13/smartly-save-stashes.html#comment-7214168</link><description>&lt;p&gt;Also on the topic of stashes... gitk can help you visualize what's going on.&lt;/p&gt;&lt;p&gt;gitk stash&lt;br&gt;gitk 'stash@{2}'&lt;br&gt;gitk 'stash@{yesterday}'&lt;br&gt;gitk --all&lt;/p&gt;&lt;p&gt;Basically you can operate on the 'stash' ref as if it were any other ref.  After all, 'git stash list' is the same as saying 'git reflog show stash'.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BartTrojanowski</dc:creator><pubDate>Sat, 14 Mar 2009 11:40:34 -0000</pubDate></item><item><title>Re: git ready &amp;raquo; get a file from a specific revision</title><link>http://gitready.com/intermediate/2009/02/27/get-a-file-from-a-specific-revision.html#comment-6705078</link><description>&lt;p&gt;If you're a vim user, grab &lt;a href="http://www.vim.org/scripts/script.php?script_id=2185" rel="nofollow noopener" target="_blank" title="http://www.vim.org/scripts/script.php?script_id=2185"&gt;http://www.vim.org/scripts/...&lt;/a&gt; and then you can do:&lt;/p&gt;&lt;p&gt;vim branch:path/file.c&lt;/p&gt;&lt;p&gt;or even&lt;/p&gt;&lt;p&gt;:e branch:path/file.c&lt;/p&gt;&lt;p&gt;when inside vim.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BartTrojanowski</dc:creator><pubDate>Fri, 27 Feb 2009 12:58:20 -0000</pubDate></item><item><title>Re: git ready &amp;raquo; finding remote branches</title><link>https://disqus.com/home/discussion/git-ready/git_ready_raquo_finding_remote_branches/#comment-6251544</link><description>&lt;p&gt;Also related:  git branch -r&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BartTrojanowski</dc:creator><pubDate>Fri, 13 Feb 2009 19:46:55 -0000</pubDate></item><item><title>Re: git ready &amp;raquo; easily fetching upstream changes</title><link>http://gitready.com/intermediate/2009/02/12/easily-fetching-upstream-changes.html#comment-6229803</link><description>&lt;p&gt;How about...&lt;/p&gt;&lt;p&gt;git config --global alias.up "remote update"&lt;/p&gt;&lt;p&gt;It doesn't merge... but that's probably better for most people.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BartTrojanowski</dc:creator><pubDate>Thu, 12 Feb 2009 21:13:58 -0000</pubDate></item><item><title>Re: git ready &amp;raquo; finding what has been changed</title><link>http://gitready.com/intermediate/2009/01/30/finding-what-has-been-changed.html#comment-5741157</link><description>&lt;p&gt;git log --stat is also useful.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BartTrojanowski</dc:creator><pubDate>Sun, 01 Feb 2009 00:39:55 -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-5516126</link><description>&lt;p&gt;For those that use ZSH and not BASH you may want to look at:&lt;/p&gt;&lt;p&gt;&lt;a href="http://www.jukie.net/~bart/blog/zsh-git-prompt" rel="nofollow noopener" target="_blank" title="http://www.jukie.net/~bart/blog/zsh-git-prompt"&gt;http://www.jukie.net/~bart/blog/zsh-git-prompt&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BartTrojanowski</dc:creator><pubDate>Sat, 24 Jan 2009 11:08:42 -0000</pubDate></item><item><title>Re: git ready » pushing and pulling</title><link>http://gitready.com/beginner/2009/01/21/pushing-and-pulling.html#comment-5468327</link><description>&lt;p&gt;Hmm, about the diagram... why does the 'rebase' command talk to a remote?  I think that's wrong.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BartTrojanowski</dc:creator><pubDate>Thu, 22 Jan 2009 13:58:54 -0000</pubDate></item><item><title>Re: git ready &amp;raquo; bend logs to your will</title><link>http://gitready.com/advanced/2009/01/20/bend-logs-to-your-will.html#comment-5412020</link><description>&lt;p&gt;Don't forget&lt;br&gt;&lt;/p&gt;&lt;blockquote&gt;&lt;br&gt;    git log -S"match something in the patch"&lt;br&gt;&lt;/blockquote&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BartTrojanowski</dc:creator><pubDate>Tue, 20 Jan 2009 21:22:54 -0000</pubDate></item></channel></rss>