On Mon, Mar 24, 2014 at 4:10 AM, Erik Carstensen <[email protected]> wrote: > It's stupid to export an empty patch, but it should either > 1. give a clean error message > 2. work, but give a warning > 3. just work > > I would prefer (1): The problem was triggered when I forgot to refresh after > a push with conflicts; I did not actually mean to export an empty patch. > > If you go for (2) or (3), I suppose we should also test that 'stg import' > can import the empty patch.
Hmm. I'd say (2) or (3) is right---an empty patch is still a patch (and might even contain a valuable commit message), and it seems harsh to trigger an error for it, especially if one is exporting several patches and just one of them is empty. A warning might be useful, though. -- Karl Wiberg, [email protected] subrabbit.wordpress.com www.treskal.com/kalle _______________________________________________ stgit-users mailing list [email protected] https://mail.gna.org/listinfo/stgit-users
