Re: [PATCH] send-email: detect and offer to skip backup files

2016-04-12 Thread Junio C Hamano
Stefan Beller writes: > Once I made the mistake to not remove a previous patch series I had, > such that there was: > > -coverletter.patch (newly worded) > 0001-bla-from-new-series > 0001-foo-from-old-series > 0002-... > ... > > `git send-email 0*` then sent out a totally bogus seri

Re: [PATCH] send-email: detect and offer to skip backup files

2016-04-12 Thread Junio C Hamano
Eric Sunshine writes: > I still have the same question[1] as last time I reviewed this patch: > Should default be 'n', or am I misunderstanding? Yes, you are right and no, there is no misunderstanding. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a me

Re: [PATCH] send-email: detect and offer to skip backup files

2016-04-12 Thread Stefan Beller
On Tue, Apr 12, 2016 at 3:53 PM, Junio C Hamano wrote: > Diligent people save output from format-patch to files, proofread > and edit them and then finally send the result out. If the > resulting files are sent out with "git send-email 0*", this ends up > sending backup files (e.g. 0001-X.patch.b

Re: [PATCH] send-email: detect and offer to skip backup files

2016-04-12 Thread Eric Sunshine
On Tue, Apr 12, 2016 at 6:53 PM, Junio C Hamano wrote: > Diligent people save output from format-patch to files, proofread > and edit them and then finally send the result out. If the > resulting files are sent out with "git send-email 0*", this ends up > sending backup files (e.g. 0001-X.patch.b

[PATCH] send-email: detect and offer to skip backup files

2016-04-12 Thread Junio C Hamano
Diligent people save output from format-patch to files, proofread and edit them and then finally send the result out. If the resulting files are sent out with "git send-email 0*", this ends up sending backup files (e.g. 0001-X.patch.backup or 0001-X.patch~) left by their editors next to the final