From: Abdullah Siddiqui <siddiquiabdullah92@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Gabriel Ravier <gabravier@gmail.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: C++ version for GCC development
Date: Tue, 8 Feb 2022 22:40:23 -0500 [thread overview]
Message-ID: <CADgxu+SmnNE9Y8FmOsDr=OSkfufOk+-v-1g2Y_=oxAyd-FF4gw@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdQnqNKCjg1hwckyciVvMS6MYiNkaD0aGPR2h7PyVoG9hA@mail.gmail.com>
Thank you.
On Tue, Feb 8, 2022, 12:07 PM Jonathan Wakely, <jwakely.gcc@gmail.com>
wrote:
>
>
> On Tue, 8 Feb 2022 at 17:04, Abdullah Siddiqui <
> siddiquiabdullah92@gmail.com> wrote:
>
>> Jonathan,
>>
>> Oh ok. I already checked out GCC from your second link
>> https://gcc.gnu.org/git.html. I just wanted to know if I could access
>> the code from the browser itself (like on GitHub).
>>
>
> Like it says at that link, you can browse it at
> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git
>
>
next prev parent reply other threads:[~2022-02-09 3:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 22:26 Abdullah Siddiqui
2022-02-07 22:56 ` Jonathan Wakely
2022-02-07 23:04 ` Abdullah Siddiqui
2022-02-07 23:35 ` Jonathan Wakely
2022-02-08 0:17 ` Abdullah Siddiqui
2022-02-08 2:21 ` Gabriel Ravier
2022-02-08 2:42 ` Abdullah Siddiqui
2022-02-08 2:44 ` Abdullah Siddiqui
2022-02-08 7:49 ` Jonathan Wakely
2022-02-08 16:56 ` Abdullah Siddiqui
2022-02-08 16:59 ` Jonathan Wakely
2022-02-08 17:04 ` Abdullah Siddiqui
2022-02-08 17:07 ` Jonathan Wakely
2022-02-09 3:40 ` Abdullah Siddiqui [this message]
2022-03-03 9:04 ` Abdullah Siddiqui
2022-03-03 10:35 ` Jonathan Wakely
2022-03-04 3:07 ` Abdullah Siddiqui
2022-03-04 6:29 ` Xi Ruoyao
2022-03-04 23:01 ` Abdullah Siddiqui
2022-03-04 9:13 ` Jonathan Wakely
2022-03-04 23:03 ` Abdullah Siddiqui
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='CADgxu+SmnNE9Y8FmOsDr=OSkfufOk+-v-1g2Y_=oxAyd-FF4gw@mail.gmail.com' \
--to=siddiquiabdullah92@gmail.com \
--cc=gabravier@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@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).