From: karthik nayak <firstname.lastname@example.org> To: Git List <email@example.com> Subject: [GSOC] Introduction Date: Sat, 07 Mar 2015 16:55:26 +0530 [thread overview] Message-ID: <54FAE026.firstname.lastname@example.org> (raw) Hello everyone! I am Karthik Nayak from Bangalore, India. I am currently pursuing my B.E in Computer Science. I am very keen on contributing to Git via GSoC 2015. I have worked on one of the micro projects, I like how code is reviewed via the mailing list, It always ensures different perspectives on the same code and shows how there is always room for improvement. I have been using Git for personal work, since about two years now. The reason why I want to contribute to Git is because I can relate to what is happening in the code, since I use it regularly. I want to work on the project of "Unifying git branch -l, git tag -l, and git for-each-ref" and have been reading up on what Junio suggested in a reply to Amate Yolande. I also found a link to a previous discussion on the same topic. Is there any other discussion on the same? Do you guys have any comments? Regards -Karthik  : http://article.gmane.org/gmane.comp.version-control.git/264911  : http://article.gmane.org/gmane.comp.version-control.git/264966  : http://thread.gmane.org/gmane.comp.version-control.git/261479
next reply other threads:[~2015-03-07 11:25 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-07 11:25 karthik nayak [this message] 2019-02-24 10:05 [GSoC] Introduction Rohit Ashiwal 2019-02-24 14:47 ` Johannes Schindelin 2019-02-25 6:50 ` Christian Couder 2019-02-25 11:35 ` Rohit Ashiwal 2019-02-25 20:21 ` Christian Couder 2019-02-25 21:09 ` Eric Sunshine 2020-01-01 13:02 [GSOC] Introduction Hariom verma 2020-01-23 11:16 ` Christian Couder 2020-01-23 20:18 ` Hariom verma 2020-01-23 22:38 ` Christian Couder 2020-01-22 20:42 [GSoC] Introduction Shourya Shukla 2020-01-23 11:02 ` Christian Couder 2020-01-23 18:04 ` Shourya Shukla 2020-01-23 22:51 ` Christian Couder
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=54FAE026.email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [GSOC] Introduction' \ /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
Code repositories for project(s) associated with this 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).