git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Thomas Gummerer <t.gummerer@gmail.com>
To: Sushma Unnibhavi <sushmaunnibhavi425@gmail.com>
Cc: git@vger.kernel.org, Christian Couder <christian.couder@gmail.com>
Subject: Re: [GSOC]regarding project selection
Date: Tue, 12 Mar 2019 23:19:34 +0000	[thread overview]
Message-ID: <20190312231934.GD16414@hank.intra.tgummerer.com> (raw)
In-Reply-To: <20190312112404.GA5031@hacker-queen>

Hi,

please always Cc: the potential mentors of a microproject when you
want to discuss it.  That makes it much more likely for the mentors to
notice your email and discuss it for you.  I added Christian, who's
listed as possible mentor on the project page to Cc: here.

On 03/12, Sushma Unnibhavi wrote:

> I am interested to do a project on improving git log --oneline.I can
> program in C language,I have learnt how to send patches and I am
> also comfortable with using git.I wanted to know what are the
> prerequisites for doing the project.Can I get some help regarding
> this matter.

The prerequisites are stated on the project page.  The languages
you'll need to know are C and shell.  More importantly though, you
should get familiar enough with the project to discuss it here.

Did you read the links that are provided on the project page?  If
there is anything unclear about the project you should try to ask more
specific questions, that show that you have done your homework and
gave the proposed project a bit more thoughts.  That shows your
interest in the project, and we can give you much better answers.
Just asking for help in a very general manner makes it very hard for
us to give you a good response.

One of the criteria for choosing students is going to be how well
fleshed out the project proposal is going to be.

As an aside, the patches you sent for your microproject received a few
comments.  Apart from the project proposal, it's also important to try
and address those comments, to show how you interact with your
mentors and other people on the mailing list.

      reply	other threads:[~2019-03-12 23:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 11:24 [GSOC]regarding project selection Sushma Unnibhavi
2019-03-12 23:19 ` Thomas Gummerer [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=20190312231934.GD16414@hank.intra.tgummerer.com \
    --to=t.gummerer@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sushmaunnibhavi425@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).