<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>Toby&#039;s Technical Ramblings &#187; Git</title> <atom:link href="http://tosbourn.com/category/git/feed/" rel="self" type="application/rss+xml" /><link>http://tosbourn.com</link> <description>A web development blog.</description> <lastBuildDate>Mon, 06 Feb 2012 15:08:08 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>Using Git to create an archive of changed files.</title><link>http://tosbourn.com/2011/05/git/using-git-to-create-an-archive-of-changed-files/</link> <comments>http://tosbourn.com/2011/05/git/using-git-to-create-an-archive-of-changed-files/#comments</comments> <pubDate>Fri, 20 May 2011 11:41:02 +0000</pubDate> <dc:creator>Toby</dc:creator> <category><![CDATA[Git]]></category> <category><![CDATA[Archive]]></category><guid
isPermaLink="false">http://tosbourn.com/?p=440</guid> <description><![CDATA[Often I have found myself in a situation where it would be really nice to have an archive of the files I have recently been working on. Using two Git commands I can easily create such an archive. The first actually creates the archive; git archive -o update.zip HEAD This will create an archive of [...]]]></description> <content:encoded><![CDATA[<p>Often I have found myself in a situation where it would be really nice to have an archive of the files I have recently been working on.</p><p>Using two Git commands I can easily create such an archive.</p><p>The first actually creates the archive;</p><p><code>git archive -o update.zip HEAD</code></p><p>This will create an archive of the entire repository, which isn&#8217;t what we want in this instance but is pretty handy to know.</p><p>The archive function accepts a list of files to archive, which is what we want to do and is where our second command comes in.</p><p><code>git diff --name-only HEAD^</code></p><p>This will do the commit before the head, which is what I want most of the time but this could be changed to get files between two commits or anything you wanted, check out the help section in git for the diff command.</p><p>Finally we want to bring this all together into one nice and easy command, thus;</p><p><code>git archive -o update.zip HEAD $(git diff --name-only HEAD^)</code></p><p>This wraps our second command with $(), this gets ran first and passes the result as a parameter into our first command.</p> ]]></content:encoded> <wfw:commentRss>http://tosbourn.com/2011/05/git/using-git-to-create-an-archive-of-changed-files/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Git command to show files changed in a commit</title><link>http://tosbourn.com/2011/04/git/git-command-to-show-files-changed-in-a-commit/</link> <comments>http://tosbourn.com/2011/04/git/git-command-to-show-files-changed-in-a-commit/#comments</comments> <pubDate>Mon, 04 Apr 2011 08:39:17 +0000</pubDate> <dc:creator>Toby</dc:creator> <category><![CDATA[Git]]></category><guid
isPermaLink="false">http://www.tosbourn.com/?p=420</guid> <description><![CDATA[Recently I wanted to pull a list of changed files from an older commit from the command line. Turns out (like most things in Git) this is very easy to do. git show --name-only {commit} You can replace {commit} with the SHA1 you want to retrieve, or things like HEAD or HEAD^^]]></description> <content:encoded><![CDATA[<p>Recently I wanted to pull a list of changed files from an older commit from the command line.</p><p>Turns out (like most things in Git) this is very easy to do.</p><pre>git show --name-only {commit}</pre><p>You can replace {commit} with the SHA1 you want to retrieve, or things like HEAD or HEAD^^</p> ]]></content:encoded> <wfw:commentRss>http://tosbourn.com/2011/04/git/git-command-to-show-files-changed-in-a-commit/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Explaining Version Control (Git) in Simple Terms</title><link>http://tosbourn.com/2011/03/git/explaining-version-control-git-in-simple-terms/</link> <comments>http://tosbourn.com/2011/03/git/explaining-version-control-git-in-simple-terms/#comments</comments> <pubDate>Tue, 01 Mar 2011 14:28:37 +0000</pubDate> <dc:creator>Toby</dc:creator> <category><![CDATA[Git]]></category> <category><![CDATA[Download]]></category> <category><![CDATA[Paul Synnott]]></category> <category><![CDATA[Version Control]]></category><guid
isPermaLink="false">http://www.tosbourn.com/?p=394</guid> <description><![CDATA[Today I found a presentation that Paul Synnott made that was aimed at explaining the need for Git, or at least version control to non-developers. I thought it was an excellent way of explaining to someone who doesn&#8217;t like technical jargon, or is too inexperienced to understand it why time should be invested in using [...]]]></description> <content:encoded><![CDATA[<p>Today I found a presentation that <a
href="http://twitter.com/#!/psynnott" target="_blank">Paul Synnott</a> made that was aimed at explaining the need for Git, or at least version control to non-developers.</p><p>I thought it was an excellent way of explaining to someone who doesn&#8217;t like technical jargon, or is too inexperienced to understand it why time should be invested in using Version Control.</p><p>I asked if I could chuck it up here for others to download and he agreed, so here it is:</p><p><a
href="http://d2aucw19zh6gg9.cloudfront.net/wp-content/uploads/2011/03/GIT.pdf?9d7bd4">Git for non-devs</a></p><p>Cheers, Paul!</p> ]]></content:encoded> <wfw:commentRss>http://tosbourn.com/2011/03/git/explaining-version-control-git-in-simple-terms/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Two excellent talks on Git</title><link>http://tosbourn.com/2011/01/git/two-excellent-talks-on-git/</link> <comments>http://tosbourn.com/2011/01/git/two-excellent-talks-on-git/#comments</comments> <pubDate>Thu, 13 Jan 2011 18:55:00 +0000</pubDate> <dc:creator>Toby</dc:creator> <category><![CDATA[Git]]></category> <category><![CDATA[Linus Torvalds]]></category> <category><![CDATA[Randal Schwartz]]></category><guid
isPermaLink="false">http://www.tosbourn.com/?p=365</guid> <description><![CDATA[These two GoogleTechTalks videos compliment each other excellently and between them explain Git perfectly. The first is by Linus Torvalds and the second is by Randal Schwartz, unfortunately I cannot embed them but here are the links. Linus Torvalds talks about Git Randal Schwartz talks about Git]]></description> <content:encoded><![CDATA[<p>These two GoogleTechTalks videos compliment each other excellently and between them explain Git perfectly.  The first is by Linus Torvalds and the second is by Randal Schwartz, unfortunately I cannot embed them but here are the links.</p><ol><li><a
href="http://www.youtube.com/watch?v=4XpnKHJAok8" target="_blank">Linus Torvalds talks about Git</a></li><li><a
href="http://www.youtube.com/watch?v=8dhZ9BXQgc4" target="_blank">Randal Schwartz talks about Git</a></li></ol> ]]></content:encoded> <wfw:commentRss>http://tosbourn.com/2011/01/git/two-excellent-talks-on-git/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Useful Git Links</title><link>http://tosbourn.com/2010/06/git/useful-git-links/</link> <comments>http://tosbourn.com/2010/06/git/useful-git-links/#comments</comments> <pubDate>Tue, 22 Jun 2010 12:48:12 +0000</pubDate> <dc:creator>Toby</dc:creator> <category><![CDATA[Git]]></category><guid
isPermaLink="false">http://www.tosbourn.com/?p=270</guid> <description><![CDATA[This is a post I will be adding to over time all about links I have found useful when learning how to best use Git. Latest Edited: 21/01/12 *NEW* A successful Git branching Model &#8211; The title says it all really, a really nice way method for branching during the product life-cycle. Git &#8211; The [...]]]></description> <content:encoded><![CDATA[<p>This is a post I will be adding to over time all about links I have found useful when learning how to best use Git.</p><p><em>Latest Edited: 21/01/12</em></p><p>*NEW* <a
href="http://nvie.com/posts/a-successful-git-branching-model/" target="_blank">A successful Git branching Model</a> &#8211; The title says it all really, a really nice way method for branching during the product life-cycle.</p><p><a
title="Git Guide" href="http://rogerdudler.github.com/git-guide/" target="_blank">Git &#8211; The Simple Guide</a> &#8211; Really nice beginners guide to Git.</p><p><a
href="http://ariejan.net/2009/10/26/how-to-create-and-apply-a-patch-with-git/" target="_blank">How To Create And Apply A Patch</a> &#8211; Really good article, the only thing I would clarify is that the am command can only be used once you have set up mailing (something I have yet to do).</p><p><a
href="http://www.zorched.net/2008/04/14/start-a-new-branch-on-your-remote-git-repository/" target="_blank">Creating A New Branch On Your Remote Repository</a> &#8211; Such a simple task but one I couldn&#8217;t easily find described somewhere for the layman.</p><p><a
href="http://sysmonblog.co.uk/misc/git_by_example/" target="_blank">Git By Example</a> &#8211; This has all the basic git commands that anyone starting out with Git will want to familiarise themselves with complete with examples.</p><p><a
href="http://lwn.net/Articles/210045/" target="_blank">Branching and Merging</a> &#8211; An interesting document on branching and merging within Git.</p><p>Thanks to @<a
href="http://twitter.com/psynnott" target="_blank">psynnott</a> for contributing some links.</p> ]]></content:encoded> <wfw:commentRss>http://tosbourn.com/2010/06/git/useful-git-links/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Editing Git Repository Descriptions</title><link>http://tosbourn.com/2010/03/git/editing-git-repository-descriptions/</link> <comments>http://tosbourn.com/2010/03/git/editing-git-repository-descriptions/#comments</comments> <pubDate>Mon, 15 Mar 2010 12:39:02 +0000</pubDate> <dc:creator>Toby</dc:creator> <category><![CDATA[Git]]></category> <category><![CDATA[Repository]]></category><guid
isPermaLink="false">http://www.tosbourn.com/?p=211</guid> <description><![CDATA[It was annoying me that when viewing my repositories online the descriptions for them all were the generic &#8216;Unnamed repository; edit this file &#8216;description&#8217; to name the repository.&#8217; It doesn&#8217;t really tell you in any tutorial what you need to do when setting up a repository to get a description (or at least any I [...]]]></description> <content:encoded><![CDATA[<p>It was annoying me that when viewing my repositories online the descriptions for them all were the generic &#8216;Unnamed repository; edit this file &#8216;description&#8217; to name the repository.&#8217;</p><p>It doesn&#8217;t really tell you in any tutorial what you need to do when setting up a repository to get a description (or at least any I have followed) but the fix is very simple.</p><p>In the your git repository you should see a text file named description.</p><p>Edit it with your text editor of choice and whatever you have as the contents will be your repository description.</p><blockquote><p>vi gitRepository.git/description</p></blockquote><p>Done!</p> ]]></content:encoded> <wfw:commentRss>http://tosbourn.com/2010/03/git/editing-git-repository-descriptions/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Served from: tosbourn.com @ 2012-02-07 05:26:06 by W3 Total Cache -->
