<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/patch-process/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/patch-process/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 12 Dec 2006 21:23:34 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/patch-process/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Support SVN projects</title><link>https://sourceforge.net/p/patch-process/feature-requests/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Currently, only CVS projects are supported.  We need to support SVN projects as well.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric Pabst</dc:creator><pubDate>Tue, 12 Dec 2006 21:23:34 -0000</pubDate><guid>https://sourceforge.netfb17938c6bf43b40e4228c499ab7267a957192ed</guid></item><item><title>Make GUI able to store settings for future use</title><link>https://sourceforge.net/p/patch-process/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When the user enters settings, the settings should be storable as the defaults for the "project" that will be prepopulated next time.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric Pabst</dc:creator><pubDate>Tue, 12 Dec 2006 21:11:49 -0000</pubDate><guid>https://sourceforge.netdacabfa2e022d39f0e58700904d8bac5f406a832</guid></item><item><title>Add options to GUI, including test.target</title><link>https://sourceforge.net/p/patch-process/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;In the GUI where the CVS comment is enterred, it should allow specifying the following:&lt;br /&gt;
-skip.commit&lt;br /&gt;
-skip.test&lt;br /&gt;
-ant target&lt;br /&gt;
-checkout module&lt;br /&gt;
-apply-patch relative dir&lt;br /&gt;
-test relative dir&lt;br /&gt;
etc.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric Pabst</dc:creator><pubDate>Tue, 12 Dec 2006 21:10:20 -0000</pubDate><guid>https://sourceforge.net5df4cceb53f33308230f6b3a3ded3e1c06567574</guid></item><item><title>No longer require project configuration on server</title><link>https://sourceforge.net/p/patch-process/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Currently, in order to use the Patch Process on a project, you have to create a project configuration file, and either SCP it or use CVS to transfer it over to the server as well.  This is burdensome and when many projects exist, and new ones are created often, this is enough pain to consider other alternatives such as running the Patch Process locally or not using it at all.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric Pabst</dc:creator><pubDate>Tue, 12 Dec 2006 20:58:40 -0000</pubDate><guid>https://sourceforge.net81a82ad08ed07fe8483d85894042bbce97cb0fe7</guid></item></channel></rss>