<?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: git tips</title>
	<atom:link href="http://tribulaciones.org/2008/12/git-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://tribulaciones.org/2008/12/git-tips/</link>
	<description>A blog about me and whatever insterests me</description>
	<lastBuildDate>Mon, 06 Apr 2009 12:59:07 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jsogo</title>
		<link>http://tribulaciones.org/2008/12/git-tips/comment-page-1/#comment-18</link>
		<dc:creator>jsogo</dc:creator>
		<pubDate>Thu, 25 Dec 2008 23:13:56 +0000</pubDate>
		<guid isPermaLink="false">http://tribulaciones.org/?p=64#comment-18</guid>
		<description>Well, this is another option. Having get-orig-source is doable, as you say, but using git is also interesting here. You don&#039;t lose the ability of use quilt and if you&#039;re concerned about keeping upstream tarball as it was got from upstream, you can use pristine-tar.
But of course every option is good as far as you are comfortable with it.</description>
		<content:encoded><![CDATA[<p>Well, this is another option. Having get-orig-source is doable, as you say, but using git is also interesting here. You don&#8217;t lose the ability of use quilt and if you&#8217;re concerned about keeping upstream tarball as it was got from upstream, you can use pristine-tar.<br />
But of course every option is good as far as you are comfortable with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Np237</title>
		<link>http://tribulaciones.org/2008/12/git-tips/comment-page-1/#comment-17</link>
		<dc:creator>Np237</dc:creator>
		<pubDate>Thu, 25 Dec 2008 22:45:17 +0000</pubDate>
		<guid isPermaLink="false">http://tribulaciones.org/?p=64#comment-17</guid>
		<description>You can have the whole source without versioning it. When I want another version, I just edit the changelog, run &quot;debian/rules get-orig-source&quot;, and I can start working on my quilt series in a temporary directory.</description>
		<content:encoded><![CDATA[<p>You can have the whole source without versioning it. When I want another version, I just edit the changelog, run &#8220;debian/rules get-orig-source&#8221;, and I can start working on my quilt series in a temporary directory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jsogo</title>
		<link>http://tribulaciones.org/2008/12/git-tips/comment-page-1/#comment-16</link>
		<dc:creator>jsogo</dc:creator>
		<pubDate>Thu, 25 Dec 2008 22:39:04 +0000</pubDate>
		<guid isPermaLink="false">http://tribulaciones.org/?p=64#comment-16</guid>
		<description>I was not meaning that. If you see every package I have, patches are always in debian/patch (dpatch format). I have even talked about topgit, which is a tool to make using git and quilt easy.
Of course patching directly upstream source is not a good idea, and should be discouraged. But having the whole source available in the dir you&#039;re working makes things easier.</description>
		<content:encoded><![CDATA[<p>I was not meaning that. If you see every package I have, patches are always in debian/patch (dpatch format). I have even talked about topgit, which is a tool to make using git and quilt easy.<br />
Of course patching directly upstream source is not a good idea, and should be discouraged. But having the whole source available in the dir you&#8217;re working makes things easier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Np237</title>
		<link>http://tribulaciones.org/2008/12/git-tips/comment-page-1/#comment-15</link>
		<dc:creator>Np237</dc:creator>
		<pubDate>Thu, 25 Dec 2008 22:16:07 +0000</pubDate>
		<guid isPermaLink="false">http://tribulaciones.org/?p=64#comment-15</guid>
		<description>Putting the whole source code in the VCS makes it completely awkward to update the package using &quot;apt-get source&quot;, since all changes to the upstream source are merged in a single big diff.

The way most packaging subprojects use SVN is merely as a versioned data store. The source changes are managed by quilt, which makes it much easier to deal with the package outside of the repository.</description>
		<content:encoded><![CDATA[<p>Putting the whole source code in the VCS makes it completely awkward to update the package using &#8220;apt-get source&#8221;, since all changes to the upstream source are merged in a single big diff.</p>
<p>The way most packaging subprojects use SVN is merely as a versioned data store. The source changes are managed by quilt, which makes it much easier to deal with the package outside of the repository.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- www.000webhost.com Analytics Code -->
<script type="text/javascript" src="http://analytics.hosting24.com/count.php"></script>
<noscript><a href="http://www.hosting24.com/"><img src="http://analytics.hosting24.com/count.php" alt="web hosting" /></a></noscript>
<!-- End Of Analytics Code -->
