jira-importer commented on issue #442: URL: https://github.com/apache/maven-deploy-plugin/issues/442#issuecomment-2771541197
**[Jerome Lacoste](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=lacostej)** commented To Brett: "I've had problems with your method of patches before Jerome - can you use "svn diff" instead of taking copies of the files and using diff? We need to know what the source revision was." The reason I don't use svn diff directly is I often have several patches waiting on the same project. For example I submitted that one in a serie of 3 patches. I cannot then use svn diff to create my patch. I would have to create each patch independently of the other and 1- it is often not possible, 2- that means I would have to update my patch when a precedent one is checked in. So svn diff is not an option in some cases given the way I work (in batch). So I use 'quilt' to handle the patches. It is supposed to work. I've used it successfully on all the other projects I am working on. But I sometimes make a mistake, and that render the patch not usable. I will improve my discipline and make sure that I better test apply my patch stack before submission. Maybe should I only submit them as a group (that's what is done in other projects)? Sorry if that caused you some issues but I think that this is still the correct way to go for me. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
