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

Suggested Project Ideas (was Re: Anything I can contribute?)

From
Bagas Sanjaya <bagasdotme@gmail.com>
Date
Nov 14, 2021, 07:17 UTC
Message-ID
<98f2d5f1-4282-4011-ee56-0756da24b1a8@gmail.com>
In-Reply-To
<547972d2-36fe-4acd-b9fa-747320addfa6@gmail.com>
On 13/11/21 17.41, Saksham Mittal wrote:
Show 5 quoted lines
> Most searches of the mailing list for "[BUG]", "bug" etc. yield scores
> of results for patches other people have already submitted, which are
> likely being looked over by experienced maintainers anyway. How do we
> find issues in the mailing list, especially ones that are better suited
> to a beginner?
Breaking the thread.

I think you should check for open bugs against Git package for your distribution first, then come up here with bugfixes.

For project ideas, you can try converting/rewriting git-request-pull.sh in C. When converting, you can also add `-o/--output` option to write PR message to a file instead of stdout. You may want to mark PR message strings for i18n if you want.

-- 
An old man doll... just what I always wanted! - Clara
Previous: Saksham Mittal
Message 3 of 3 in “Anything I can contribute?”
  1. Deng KaishengNov 13, 2021
  2. Saksham MittalNov 13, 2021
  3. Suggested Project Ideas (was Re: Anything I can contribute?)Bagas Sanjaya, Nov 14, 2021

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.