git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sidhant Sharma <tigerkid001@gmail.com>
To: git@vger.kernel.org
Subject: GSoC 2016 Microproject
Date: Sat, 27 Feb 2016 18:34:57 +0530	[thread overview]
Message-ID: <56D19EF9.3070702@gmail.com> (raw)

Hi everyone,


I'm Sidhant Sharma. I'm looking to participate in GSoC 2016 (and contribute  
to Git in general as well). I read up the pages relating to participation  
in GSoC and selected the microproject "Add configuration options for some  
commonly used command-line options". I have some queries regarding this  
though:

1. I believe the option can be added by a reassignment of the `verbose`  
variable in `parse_and_validate_options` function inside the  
`builtin/commit.c`. It can be a logical OR between the `verbose` (which was  
parsed by the argument parser) and the value obtained by using  
`git_config_get_bool("command.verbose", &opt_verbose)`. Am I thinking on  
the right lines?

2. Should I also add an option to override the configuration for verbose?

3. The microproject title suggests there can more such options, so are  
there more to be added?


Thanks in advance.



Regards

Sidhant Sharma [:tk]

             reply	other threads:[~2016-02-27 13:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 13:04 Sidhant Sharma [this message]
2016-02-27 13:28 ` GSoC 2016 Microproject 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
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=56D19EF9.3070702@gmail.com \
    --to=tigerkid001@gmail.com \
    --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).