https://sourceforge.net/p/patch-process/feature-requests/2006-12-12T21:23:34ZRecent changes to feature-requests2006-12-12T21:23:34Z2006-12-12T21:23:34ZEric Pabsthttps://sourceforge.net/u/pabstec/https://sourceforge.netfb17938c6bf43b40e4228c499ab7267a957192ed

<div class="markdown_content"><p>Currently, only CVS projects are supported. We need to support SVN projects as well.</p></div>

2006-12-12T21:11:49Z2006-12-12T21:11:49ZEric Pabsthttps://sourceforge.net/u/pabstec/https://sourceforge.netdacabfa2e022d39f0e58700904d8bac5f406a832

<div class="markdown_content"><p>When the user enters settings, the settings should be storable as the defaults for the "project" that will be prepopulated next time.</p></div>

2006-12-12T21:10:20Z2006-12-12T21:10:20ZEric Pabsthttps://sourceforge.net/u/pabstec/https://sourceforge.net5df4cceb53f33308230f6b3a3ded3e1c06567574

<div class="markdown_content"><p>In the GUI where the CVS comment is enterred, it should allow specifying the following:<br /> -skip.commit<br /> -skip.test<br /> -ant target<br /> -checkout module<br /> -apply-patch relative dir<br /> -test relative dir<br /> etc.</p></div>

2006-12-12T20:58:40Z2006-12-12T20:58:40ZEric Pabsthttps://sourceforge.net/u/pabstec/https://sourceforge.net81a82ad08ed07fe8483d85894042bbce97cb0fe7

<div class="markdown_content"><p>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.</p></div>