[prev in list] [next in list] [prev in thread] [next in thread]
List: git
Subject: Re: [PATCH 1/1] [Outreachy] merge-ours: include parse-options
From: Johannes Schindelin <Johannes.Schindelin () gmx ! de>
Date: 2019-10-30 21:58:39
Message-ID: nycvar.QRO.7.76.6.1910302257480.46 () tvgsbejvaqbjf ! bet
[Download RAW message or body]
Hi Junio,
On Wed, 30 Oct 2019, Junio C Hamano wrote:
> "george espinoza via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
> > From: george espinoza <gespinoz2019@gmail.com>
> >
> > Teach this command which currently handles its own argv to use
> > parse-options instead because parse-options helps make sure we handle
> > user input like -h in a standardized way across the project.
>
> Sorry, but why do we even want to do this?
It _is_ a command you can run via `git merge-ours` by mistake. Don't you
think it would be nice for users to at least get a synopsis?
Ciao,
Dscho
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic