From: Sidhant Sharma <tigerkid001@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org
Subject: Re: GSoC 2016 Microproject
Date: Tue, 1 Mar 2016 17:08:54 +0530 [thread overview]
Message-ID: <56D57F4E.7000402@gmail.com> (raw)
In-Reply-To: <vpqfuwbbjlx.fsf@anie.imag.fr>
> If you use PARSE_OPT_HIDDEN, I think you don't need to specify a message. Otherwise, the documentation only has value if it contains more than just the option name, but that is the hard part if you're not familiar with the code. The best place to find documentation is in the history (git blame the file and see if the commit message introducing the option enlightens you). But that's why I said this didn't have to be part of the microproject: writting good doc requires a good understanding of the whole thing ...
I used OPT_HIDDEN_BOOL for all except for reject-thin-pack-for-testing, where I used PARSE_OPT_HIDDEN. I ran the test locally and also on Travis, and the all tests passed. How do I proceed now?
Thanks and regards,
Sidhant Sharma [:tk]
next prev parent reply other threads:[~2016-03-01 11:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 13:04 GSoC 2016 Microproject Sidhant Sharma
2016-02-27 13:28 ` Matthieu Moy
2016-02-27 15:20 ` Sidhant Sharma
2016-02-27 16:12 ` Matthieu Moy
2016-02-28 10:12 ` Sidhant Sharma
2016-02-29 14:51 ` Sidhant Sharma
2016-02-29 15:04 ` Matthieu Moy
2016-02-29 15:32 ` Sidhant Sharma
2016-02-29 15:51 ` Matthieu Moy
2016-03-01 11:38 ` Sidhant Sharma [this message]
2016-03-01 12:22 ` Thomas Gummerer
-- strict thread matches above, loose matches on Subject: below --
2016-02-19 8:59 GSoC 2016: Microproject Mehul Jain
2016-02-19 13:03 ` Matthieu Moy
2016-02-19 17:39 ` Mehul Jain
2016-02-19 17:50 ` Stefan Beller
2016-02-19 18:32 ` Mehul Jain
2016-02-20 14:43 ` Mehul Jain
2016-02-21 4:55 ` Matthieu Moy
2016-02-21 16:04 ` Mehul Jain
2016-02-21 18:52 ` Matthieu Moy
2016-02-22 8:10 ` Karthik Nayak
2016-02-22 10:12 ` Mehul Jain
2016-02-22 10:20 ` Duy Nguyen
2016-02-22 10:30 ` Mehul Jain
2016-02-22 11:21 ` Duy Nguyen
2016-02-22 12:28 ` Mehul Jain
2016-02-22 10:21 ` Lars Schneider
2016-02-22 10:30 ` Lars Schneider
2016-02-21 16:02 ` Mehul Jain
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=56D57F4E.7000402@gmail.com \
--to=tigerkid001@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).