git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Saksham Mittal <gotlouemail@gmail.com>,
	Deng Kaisheng <kaisheng.deng@u.nus.edu>,
	git@vger.kernel.org
Subject: Suggested Project Ideas (was Re: Anything I can contribute?)
Date: Sun, 14 Nov 2021 14:17:23 +0700	[thread overview]
Message-ID: <98f2d5f1-4282-4011-ee56-0756da24b1a8@gmail.com> (raw)
In-Reply-To: <547972d2-36fe-4acd-b9fa-747320addfa6@gmail.com>

On 13/11/21 17.41, Saksham Mittal wrote:
> 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

      reply	other threads:[~2021-11-14  7:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13  8:33 Anything I can contribute? Deng Kaisheng
2021-11-13 10:41 ` Saksham Mittal
2021-11-14  7:17   ` Bagas Sanjaya [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=98f2d5f1-4282-4011-ee56-0756da24b1a8@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gotlouemail@gmail.com \
    --cc=kaisheng.deng@u.nus.edu \
    /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).