git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Contribute Code to Git

From
Junio C Hamano <gitster@pobox.com>
Date
May 3, 2015, 17:47 UTC
Message-ID
<xmqqtwvtv9hv.fsf@gitster.dls.corp.google.com>
In-Reply-To
<loom.20150430T124609-727@post.gmane.org>
Alangi Derick Ndimnain <alangiderick@gmail.com> writes:
>     I will like to have some advices and also start working on the system...
A few advices from my end are:
 - Think yourself and remember what annoyances, troubles and issues
   you had with your daily use of Git.  They are good problems to
   tackle, as you have a first-hand experience with them.  Don't
   go hunting for "problems to solve".  That will likely end up
   wasting your time (and reviewers' time as well).
 - Start by reading everything other people post, until you notice
   whose posts are worth your time reading.  And then, concentrate
   on following the discussion threads they are involved in, to
   learn how the best discussions are carried out on this list.
Thanks.  
Previous: karthik nayakNext: Alangi Derick
Message 3 of 4 in “Contribute Code to Git”
  1. Alangi Derick NdimnainApr 30, 2015
  2. karthik nayakApr 30, 2015
  3. Junio C HamanoMay 3, 2015
  4. Alangi DerickMay 3, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.