# Clarification required for microproject "Add configuration options for some commonly used command-line options"

2 messages from 2015-03-10 to 2015-03-10. Participants: Koosha Khajehmoogahi, Junio C Hamano.
Thread: https://gitlist.dev/t/38778

## Koosha Khajehmoogahi, 2015-03-10 23:29

Subject: Clarification required for microproject "Add configuration options for some commonly used command-line options"
Message-ID: <54FF7E63.3030902@gmail.com>
URL: https://gitlist.dev/e/54FF7E63.3030902%40gmail.com

```
Does this microproject require the feature to be a generic one for every
possible command or should it be limited to some particular commands?

```

## Junio C Hamano, 2015-03-10 23:43

Subject: Re: Clarification required for microproject "Add configuration options for some commonly used command-line options"
Message-ID: <xmqq7fuoxvt0.fsf@gitster.dls.corp.google.com>
URL: https://gitlist.dev/e/xmqq7fuoxvt0.fsf%40gitster.dls.corp.google.com
In-Reply-To: <54FF7E63.3030902@gmail.com>

```
Koosha Khajehmoogahi <koosha.khajeh@gmail.com> writes:

> Does this microproject require the feature to be a generic one for every
> possible command or should it be limited to some particular commands?

The Micro is written lazily so that by writing that entry once, it
can tell many students to work on many different Git subcommands and
their options in parallel ;-)

"generic for every possible" is very hard to do it well and make it
useful, and is unsuitably big undertaking for a microproject, I
would think.

```
