Hi,<br><br>It looks like I don&#39;t have permissions to commit into this patch folder.<br>so I attached my patch that computes distance between two vectors.<br>and I would be very happy to have the permissions to commit there.<br>
<br>Dina<br><br><div class="gmail_quote">On Fri, Dec 12, 2008 at 2:25 PM, Daniel Russel <span dir="ltr">&lt;<a href="mailto:drussel@gmail.com">drussel@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I stuck the outstanding patches I know of in kernel/doc/patch.<br>
<br>
How does one apply a patch generated by svn which involved moving files? Taking the diff and then using patch doesn&#39;t seem to do the right thing. Or is the system just broken for such changes?<div><div></div><div class="Wj3C7c">
<br>
<br>
<br>
On Dec 11, 2008, at 8:07 PM, Seung Joong Kim wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I also think this is a good idea<br>
<br>
Daniel Russel wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I suggest we change the process for submitting patches to the following:<br>
- have a directory writable by everyone such as IMP/patch<br>
- to submit a patch, foo, check in trunk/patch/foo.patch and truck/patch/foo.readme with the patch and a description, respectively<br>
- send a short email to imp-dev<br>
- when Ben commits the patch, he removes the files from SVN<br>
<br>
The advantage of this system is:<br>
- it is easy to see keep track of what patches have been submitted but not committed.<br>
- it is easy to update patches that have been submitted but not yet committed<br>
- it is easy to apply patches that have not yet been committed to your copy of IMP, so is is less problematic when patches don&#39;t get committed for a long time.<br>
- no more having to get files to your email<br>
- all the submitted patches are listed in one place for ben to see<br>
- the submitted doesn&#39;t have to manually clean how his records of the patch when Ben submits it.<br>
<br>
Anyone have improvements? I&#39;ll try out such a system with my next patch.<br>
_______________________________________________<br>
IMP-dev mailing list<br>
<a href="mailto:IMP-dev@salilab.org" target="_blank">IMP-dev@salilab.org</a><br>
<a href="https://salilab.org/mailman/listinfo/imp-dev" target="_blank">https://salilab.org/mailman/listinfo/imp-dev</a><br>
</blockquote>
<br>
_______________________________________________<br>
IMP-dev mailing list<br>
<a href="mailto:IMP-dev@salilab.org" target="_blank">IMP-dev@salilab.org</a><br>
<a href="https://salilab.org/mailman/listinfo/imp-dev" target="_blank">https://salilab.org/mailman/listinfo/imp-dev</a><br>
</blockquote>
<br>
_______________________________________________<br>
IMP-dev mailing list<br>
<a href="mailto:IMP-dev@salilab.org" target="_blank">IMP-dev@salilab.org</a><br>
<a href="https://salilab.org/mailman/listinfo/imp-dev" target="_blank">https://salilab.org/mailman/listinfo/imp-dev</a><br>
</div></div></blockquote></div><br>