From: Junio C Hamano <gitster@pobox.com>
To: Koosha Khajehmoogahi <koosha.khajeh@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Clarification required for microproject "Add configuration options for some commonly used command-line options"
Date: Tue, 10 Mar 2015 16:43:55 -0700 [thread overview]
Message-ID: <xmqq7fuoxvt0.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <54FF7E63.3030902@gmail.com> (Koosha Khajehmoogahi's message of "Wed, 11 Mar 2015 00:29:39 +0100")
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.
prev parent reply other threads:[~2015-03-10 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 23:29 Clarification required for microproject "Add configuration options for some commonly used command-line options" Koosha Khajehmoogahi
2015-03-10 23:43 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq7fuoxvt0.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=koosha.khajeh@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.