From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: fortran@gcc.gnu.org, kargl@gcc.gnu.org
Subject: Re: co-arrays and libgfortran
Date: Mon, 21 Dec 2020 07:18:47 -0800 [thread overview]
Message-ID: <20201221151847.GA11406@troutmask.apl.washington.edu> (raw)
In-Reply-To: <c36045c5-d404-2967-1585-4df6f677d7c2@netcologne.de>
On Mon, Dec 21, 2020 at 02:15:30PM +0100, Thomas Koenig wrote:
>
> Hi Steve,
>
> > One of these days, I'll figure a way to grab Nicolas and
> > your work. My svn gcc tree is almost a year out of date.
>
> This can be done rather easily via github.
>
> Go to https://github.com/gcc-mirror/gcc/tree/devel/coarray_native
>
> and choose "Download Zip" or download via svn.
>
disclaimer: I have zero, nada, nil, none, experience with git.
That URL appears to take me to the coarray_native branch. If I click
on the 'clone' link, I see https://github.com/gcc-mirror/gcc.git.
Is that for a complete gcc repository or specific to your branch?
IOW, if I clone from that URL, do I need to do any git voodoo
magic incantation to get to the branch?
--
Steve
next prev parent reply other threads:[~2020-12-21 15:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 4:28 Steve Kargl
2020-12-18 12:26 ` Thomas Koenig
2020-12-18 15:52 ` Steve Kargl
2020-12-19 21:59 ` Steve Kargl
2020-12-20 10:52 ` Thomas Koenig
2020-12-20 17:47 ` Steve Kargl
2020-12-21 1:04 ` Steve Kargl
2020-12-21 2:01 ` Damian Rouson
2020-12-21 13:15 ` Thomas Koenig
2020-12-21 15:18 ` Steve Kargl [this message]
2020-12-21 23:44 ` Thomas Koenig
2020-12-22 0:18 ` Steve Kargl
2020-12-22 1:40 ` Steve Kargl
2020-12-22 10:04 ` Thomas Koenig
2020-12-22 18:32 ` Steve Kargl
2020-12-22 19:33 ` Steve Kargl
2020-12-22 20:12 ` Steve Kargl
2020-12-22 20:20 ` Steve Kargl
2020-12-22 22:08 ` Steve Kargl
2020-12-22 22:22 ` Steve Kargl
2020-12-22 23:24 ` Steve Kargl
2020-12-22 23:46 ` Thomas Koenig
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=20201221151847.GA11406@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=kargl@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).