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. Merging different actions in single commands may spare some typing time, but will also make the interface more confusing, and will increase the work required for maintenance. What's more, you'll hit the problem that different people will ask for different "bundled" commands, with different default flags. So I think we better stick to the UNIX philosophy, and have commands doing just one thing and doing it well. If you really want to save some typing time, either give a try to extended shell completion (this really rocks) or set up some shell function of your own. 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. This won't let you test whether the patched tree still compiles cleanly though, which is why I use import+push myself. Thanks, -- Jean Delvare _______________________________________________ Quilt-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/quilt-dev
