From: Jeff King <peff@peff.net>
To: Christian Couder <christian.couder@gmail.com>
Cc: trickygitninja@gmail.com, git <git@vger.kernel.org>
Subject: Re: How to start contributing
Date: Wed, 24 Oct 2018 04:19:22 -0400 [thread overview]
Message-ID: <20181024081922.GA31885@sigill.intra.peff.net> (raw)
In-Reply-To: <CAP8UFD3CDwu7OVgVmEgP2Se_bxYszcze68_bXT7=wgZaxncpzg@mail.gmail.com>
On Sat, Oct 20, 2018 at 08:47:35AM +0200, Christian Couder wrote:
> > Make “git tag –contains <id>” less chatty if <id> is invalid
> > “git tag – contains <id>” prints the whole help text if <id> is
> > invalid. It should only show the error message instead.
> > Thread: https://public-inbox.org/git/20160118215433.GB24136@sigill.intra.peff.net/
> >
> > This bug is solved using the 3rd option, but I suspect that it’s still
> > here because the 2nd option is preferred.
>
> I think it should probably have been removed from the micro-project
> list. I am CC'ing Peff as he wrote the email listing the different
> options to solve the original issue and may think otherwise.
Sorry for the reply.
Yeah, I I think the solution in 3bb0923f06 (parse-options: do not show
usage upon invalid option value, 2018-03-22) is fine. Even though it may
not have been what _I_ would have done personally, I don't think it is
worth anybody spending more brain cycles on it.
-Peff
prev parent reply other threads:[~2018-10-24 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 12:49 How to start contributing Πλάτων Κιορπελίδης
2018-10-20 6:47 ` Christian Couder
2018-10-24 8:19 ` Jeff King [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181024081922.GA31885@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=trickygitninja@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).