<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	
	>
<channel>
	<title>
	Comments on: Creating a patch file for a single commit using Git	</title>
	<atom:link href="https://yllus.com/2011/05/13/creating-a-patch-file-for-a-single-commit-using-git/feed/" rel="self" type="application/rss+xml" />
	<link>https://yllus.com/2011/05/13/creating-a-patch-file-for-a-single-commit-using-git/</link>
	<description>Management executive, software developer and cyclist hailing from Toronto, Canada.</description>
	<lastBuildDate>Wed, 31 Aug 2016 10:06:30 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>
		By: Neil Gatenby		</title>
		<link>https://yllus.com/2011/05/13/creating-a-patch-file-for-a-single-commit-using-git/#comment-318474</link>

		<dc:creator><![CDATA[Neil Gatenby]]></dc:creator>
		<pubDate>Wed, 31 Aug 2016 10:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://yllus.com/?p=1886#comment-318474</guid>

					<description><![CDATA[Very useful - thanks a lot]]></description>
			<content:encoded><![CDATA[<p>Very useful &#8211; thanks a lot</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Create A Patch File Using Git &#8211; How ot be in 2016		</title>
		<link>https://yllus.com/2011/05/13/creating-a-patch-file-for-a-single-commit-using-git/#comment-312804</link>

		<dc:creator><![CDATA[Create A Patch File Using Git &#8211; How ot be in 2016]]></dc:creator>
		<pubDate>Wed, 03 Feb 2016 16:19:05 +0000</pubDate>
		<guid isPermaLink="false">http://yllus.com/?p=1886#comment-312804</guid>

					<description><![CDATA[[&#8230;] Creating a patch file for a single commit using Git &#8230; â€“ Sully Syed. May 13, 2011. Creating a patch file for a single commit using Git. One important workflow to attempt to standardize is the method in which an organization &#8230; [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Creating a patch file for a single commit using Git &#8230; â€“ Sully Syed. May 13, 2011. Creating a patch file for a single commit using Git. One important workflow to attempt to standardize is the method in which an organization &#8230; [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: androidjago		</title>
		<link>https://yllus.com/2011/05/13/creating-a-patch-file-for-a-single-commit-using-git/#comment-283918</link>

		<dc:creator><![CDATA[androidjago]]></dc:creator>
		<pubDate>Mon, 13 Jul 2015 11:54:14 +0000</pubDate>
		<guid isPermaLink="false">http://yllus.com/?p=1886#comment-283918</guid>

					<description><![CDATA[You can also save the patch to the clipboard instead of to a file. Patch files are applied to your working copy.]]></description>
			<content:encoded><![CDATA[<p>You can also save the patch to the clipboard instead of to a file. Patch files are applied to your working copy.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Sully Syed		</title>
		<link>https://yllus.com/2011/05/13/creating-a-patch-file-for-a-single-commit-using-git/#comment-74781</link>

		<dc:creator><![CDATA[Sully Syed]]></dc:creator>
		<pubDate>Mon, 26 Nov 2012 15:17:46 +0000</pubDate>
		<guid isPermaLink="false">http://yllus.com/?p=1886#comment-74781</guid>

					<description><![CDATA[Hi alphydan - the answer to your question is that the format-patch command in Git is designed to allow you to combine one or more commits into a single patch file, and that&#039;s done by specifying a range. In this command...

[shell]
$ git format-patch -M -C b29d8f2a0e6ad5595330f62f60b978fbc5696bcb~1..b29d8f2a0e6ad5595330f62f60b978fbc5696bcb 0001-The-Feed-Importer-module-will-hook-into-Drupal-s-cron-.patch
[/shell]

...you&#039;re actually stating, please create (&quot;format&quot;) a patch that contains all of the commits from one before &lt;b&gt;b29d8f2a0e6ad5595330f62f60b978fbc5696bcb&lt;/b&gt; (this is what the ~1 denotes, &quot;one before&quot;) to the commit &lt;b&gt;b29d8f2a0e6ad5595330f62f60b978fbc5696bcb&lt;/b&gt;. 

It just so happens that we only have one patch in that range, which makes the command appear to be unnecessarily long for no reason.]]></description>
			<content:encoded><![CDATA[<p>Hi alphydan &#8211; the answer to your question is that the format-patch command in Git is designed to allow you to combine one or more commits into a single patch file, and that&#8217;s done by specifying a range. In this command&#8230;</p>
<pre class="brush: bash; title: ; notranslate">
$ git format-patch -M -C b29d8f2a0e6ad5595330f62f60b978fbc5696bcb~1..b29d8f2a0e6ad5595330f62f60b978fbc5696bcb 0001-The-Feed-Importer-module-will-hook-into-Drupal-s-cron-.patch
</pre>
<p>&#8230;you&#8217;re actually stating, please create (&#8220;format&#8221;) a patch that contains all of the commits from one before <b>b29d8f2a0e6ad5595330f62f60b978fbc5696bcb</b> (this is what the ~1 denotes, &#8220;one before&#8221;) to the commit <b>b29d8f2a0e6ad5595330f62f60b978fbc5696bcb</b>. </p>
<p>It just so happens that we only have one patch in that range, which makes the command appear to be unnecessarily long for no reason.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: alphydan		</title>
		<link>https://yllus.com/2011/05/13/creating-a-patch-file-for-a-single-commit-using-git/#comment-74703</link>

		<dc:creator><![CDATA[alphydan]]></dc:creator>
		<pubDate>Fri, 23 Nov 2012 13:15:15 +0000</pubDate>
		<guid isPermaLink="false">http://yllus.com/?p=1886#comment-74703</guid>

					<description><![CDATA[Would you mind explaining the meaning of repeating the commit hash twice, and the ~1.. in between them?

Why is it?

[shell]
$ git format-patch -M -C b29d8f2a0e6ad5595330f62f60b978fbc5696bcb~1..b29d8f2a0e6ad5595330f62f60b978fbc5696bcb 0001-The-Feed-Importer-module-will-hook-into-Drupal-s-cron-.patch
[/shell]

Instead of just

[shell]
$ git format-patch -M -C b29d8f2a0e6ad5595330f62f60b978fbc5696bcb 0001-The-Feed-Importer-module-will-hook-into-Drupal-s-cron-.patch
[/shell]]]></description>
			<content:encoded><![CDATA[<p>Would you mind explaining the meaning of repeating the commit hash twice, and the ~1.. in between them?</p>
<p>Why is it?</p>
<pre class="brush: bash; title: ; notranslate">
$ git format-patch -M -C b29d8f2a0e6ad5595330f62f60b978fbc5696bcb~1..b29d8f2a0e6ad5595330f62f60b978fbc5696bcb 0001-The-Feed-Importer-module-will-hook-into-Drupal-s-cron-.patch
</pre>
<p>Instead of just</p>
<pre class="brush: bash; title: ; notranslate">
$ git format-patch -M -C b29d8f2a0e6ad5595330f62f60b978fbc5696bcb 0001-The-Feed-Importer-module-will-hook-into-Drupal-s-cron-.patch
</pre>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
