From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Veerpal Kaur <ranotaveerpal07@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: gcc-cvs-wwwdocs or For Contributing into gcc website.
Date: Fri, 9 Apr 2021 14:58:15 +0100 [thread overview]
Message-ID: <CAH6eHdQVone9WWe6aMQ12OxAkDAnzBbSqhHb8_P8T9RduMF5gg@mail.gmail.com> (raw)
In-Reply-To: <CAKtZeZMvm8vAmVpnfQx5Xdt1_F2ZhezZ4B1hFPmfugDoSR7RkQ@mail.gmail.com>
On Fri, 9 Apr 2021 at 04:01, Veerpal Kaur via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> Dear mam/sir.
>
> I am Veerpal Kaur, I have good knowledge of HTML, CSS, Bootstrap,
> JavaScript, Reactjs, SQL, MySQL, MongoDB, etc. Now I want to contribute to
> the GCC Web site and want to make it more user-friendly.
>
> I have one problem that I am unable to find a mentor for this project.
> Please mam/sir help me so that I can contribute to this project.
>
> Please, mam/sir. I request you to provide the email of gcc-cvs-wwwdocs or
> Website mentor (Jeff Law) and the online repository where this project is
> hosted https://gcc.gnu.org/about.html#git.
I'm not sure exactly what you're asking for. gcc-cvs-wwwdocs is a
read-only mailing list, and all changes to the wwwdocs get sent there
automatically. You don't the address.
Anybody can clone the reposotiry anonymously, using the command shown
in the URL you linked to:
git clone git://gcc.gnu.org/git/gcc-wwwdocs.git
If you want to propose changes to the webpages then clone the
repository, make the changes locally, then send a patch to the
gcc-patches@gcc.gnu.org mailing list as for all patches to GCC. See
https://gcc.gnu.org/contribute.html#patches for more information.
prev parent reply other threads:[~2021-04-09 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 2:57 Veerpal Kaur
2021-04-09 13:58 ` Jonathan Wakely [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=CAH6eHdQVone9WWe6aMQ12OxAkDAnzBbSqhHb8_P8T9RduMF5gg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=ranotaveerpal07@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).