From: Paul Smith <paul@mad-scientist.net>
To: gcc@gcc.gnu.org
Subject: Re: Contribution
Date: Thu, 15 Dec 2022 11:42:21 -0500 [thread overview]
Message-ID: <e9b5d3c4fbd4b63fe577981d77c11d9f306794dc.camel@mad-scientist.net> (raw)
In-Reply-To: <CAPFh8N+hT7f4Qvqi8aPrWkvoNG7DQWkYwuYrjUmnYCHc3uNAWA@mail.gmail.com>
On Wed, 2022-12-14 at 17:32 +0200, Mohamed Atef via Gcc wrote:
> Hello all,
> As I mentioned before, I don't have much time to contribute.
> So is there any way I can contribute some medium project I can work
> on but myself in the long run? I loved this community, I contributed
> before so can you suggest some work for me?
I don't know if it's on the EasyHacks list but there's this bug with a
patch I filed years ago, that has been asked for multiple times since,
but I've never had the bandwidth to polish and submit it and it looks
like I never will.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78147
next prev parent reply other threads:[~2022-12-15 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 15:32 Contribution Mohamed Atef
2022-12-15 14:47 ` Contribution Jason Merrill
2022-12-15 16:42 ` Paul Smith [this message]
[not found] <CAOw3FZBzjtxEmbSMJDviD-td4bDM_mCMs9BQpk0SvK4EpR8N5g@mail.gmail.com>
2022-03-14 8:35 ` Fwd: Contribution farhad
2022-03-14 16:51 ` Contribution David Edelsohn
[not found] <3CB6D448.45A4FE3E@knmi.nl.suse.lists.egcs>
2002-04-12 5:54 ` contribution Andi Kleen
2002-04-12 5:58 ` contribution Toon Moene
-- strict thread matches above, loose matches on Subject: below --
2002-04-12 5:45 contribution Toon Moene
[not found] <Pine.GSO.4.31.0204112030350.15026-101000@boojum.suse.lists.egcs-patches>
2002-04-12 1:28 ` contribution Andi Kleen
2002-04-12 11:42 ` contribution Alexey Starovoytov
2002-04-12 15:15 ` contribution Toon Moene
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=e9b5d3c4fbd4b63fe577981d77c11d9f306794dc.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--cc=gcc@gcc.gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).