From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: "Stanley F." <wurfk3ks@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug Tracker
Date: Sat, 26 Mar 2011 12:42:36 +0700 [thread overview]
Message-ID: <AANLkTimWQ0vBr1u2iny9FJxrEK39C0ab_6phYFda8s6Q@mail.gmail.com> (raw)
In-Reply-To: <4D8D2E29.6090008@googlemail.com>
On Sat, Mar 26, 2011 at 7:07 AM, Stanley F. <wurfk3ks@googlemail.com> wrote:
> Good evening,
>
> I'm interested in working for git during this year's GSoC program.
> So I want to get familiar with the git code by implementing some
> patches. But I can't find a bug tracker or something where are some
> TODOs to prepare for GSOC.
> Where can I find some small tasks, I can start with to get a reference
> for my proposal?
Git list is the bug tracker (well, not exactly a bug tracker). I wish
we have a todo list too. In the mean time you can look for "low
hanging fruit" in the list archive. I found this one:
http://marc.info/?l=git&m=129986810306332
--
Duy
prev parent reply other threads:[~2011-03-26 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 0:07 Bug Tracker Stanley F.
2011-03-26 5:42 ` Nguyen Thai Ngoc Duy [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimWQ0vBr1u2iny9FJxrEK39C0ab_6phYFda8s6Q@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=wurfk3ks@googlemail.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.
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).