Re: [PATCH v3 3/9] cherry-pick: add --skip-empty option
- From
Felipe Contreras <felipe.contreras@gmail.com>
- Date
- Jun 7, 2013, 20:28 UTC
- Message-ID
- <CAMP44s05QSfR8DqbYtujo5ODfFkm0XFicH33hVF9L_dyC5=ieQ@mail.gmail.com>
- In-Reply-To
- <7vy5anxcxt.fsf@alter.siamese.dyndns.org>
On Thu, Jun 6, 2013 at 2:21 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 20 quoted lines
> Felipe Contreras <felipe.contreras@gmail.com> writes: > >> On Thu, Jun 6, 2013 at 1:30 PM, Junio C Hamano <gitster@pobox.com> wrote: >>> Felipe Contreras <felipe.contreras@gmail.com> writes: >>> >>>> Pretty much what it says on the tin. >>> >>> And a bit more, isn't it? >>> >>> The --keep-redundant-commits option implies the --allow-empty option >>> and it was perfectly acceptable to give both. By making sure that >>> only at most one of -k-r-d, -a-e or -s-e is given, this forbids that >>> usage. >>> >>> "It is implied so there is no *need* to give it redundantly" is >>> different from "It is implied so you shouldn't give it redundantly". >> >> Remove that line then. > > That's what the submitter does.
Apparently "the submitter" does everything. It seems sending 800 patches in the past 3 months is not enough work for you.
And what's the point? If nobody is interested in shifting from shell scripts to C, neither am I.
Consider this series abandoned.
-- Felipe Contreras