On 6/9/05, Jean Delvare <[EMAIL PROTECTED]> wrote: > > Hi Jerome, > > [Jerome Lacoste] > > With regard to import, as you refer to it, do you always have to do > > both quilt import followed by quilt push to detect errors? Is there an > > action that does both in one? > > I don't think there is, and am not convinced there should be.
OK. Agreed. > Also, if you have good reasons to think that a given patch will fail to > apply, or just want to test it but don't really want to apply it, a > good old "patch -p1 --dry-run < some.diff" will do. I agree. That's what I do now. But I've found cases where a given patch would apply cleanly with patch but wouldn't import correctly. Happened this morning.... Using quilt 0.39 (debian sarge). Using this patch: http://jira.public.thoughtworks.org/secure/attachment/10366/cmsynergy_patch_0608.txt I finally imported the patch manually by doing something like quilt new mypatch.diff grep +++ patch.txt | cut -d ' ' -f 2 | xargs -l1 quilt add patch < patch.txt (command line from memory, it wasn't exactly that) J _______________________________________________ Quilt-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/quilt-dev
