From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Aaron Gray <aaronngray.lists@gmail.com>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: Wanted: original ConceptGCC downloads / branch, concepts-lite branch
Date: Wed, 17 Aug 2022 15:19:54 +0100 [thread overview]
Message-ID: <8333c102-ac9c-1a31-c500-8ac042b960d3@foss.arm.com> (raw)
In-Reply-To: <CANkmNDeTfzCBqMza_V+XDXr3uU1WOk014kuv=eftE1jJLq0J6A@mail.gmail.com>
On 17/08/2022 12:42, Aaron Gray via Gcc wrote:
> Hi,
>
> I am looking for the original ConceptGCC source code, the
> https://www.generic-programming.org/software/ConceptGCC/download.html has
> all broken links and the SVN is gone.
>
> Is this available on GCC git or SVN ?
>
> Also I am wondering if the original concepts-lite code is available too
> anywhere please ?
>
> Also any pointers to the documentation for the current implementation ?
>
> Regards,
>
> Aaron
Not withstanding what others have already said, the various concepts
branches are still in the git repository, but aren't in the standard
pull set. You can use git fetch to explicitly pull them:
d743a72b52bcfaa1effd7fabe542c05a30609614 refs/dead/heads/c++-concepts
780065c813a72664bd46a354a2d26087464c74fc
refs/dead/heads/conceptgcc-branch
ce85971fd96e12d0d6675ecbc46c9a1884df766c
refs/dead/heads/cxx0x-concepts-branch
14d4dad929a01ff7179350f0251af752c3125d74
refs/deleted/r131428/heads/cxx0x-concepts-branch
I haven't looked as to which is most likely to be relevant.
R.
PS, note that these branches may not appear in some mirrors if they only
mirror the default refs/heads set.
next prev parent reply other threads:[~2022-08-17 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 11:42 Aaron Gray
2022-08-17 12:16 ` Ben Boeckel
2022-08-17 12:29 ` Aaron Gray
2022-08-17 12:46 ` Jonathan Wakely
2022-08-17 12:55 ` Jonathan Wakely
2022-08-17 13:11 ` Aaron Gray
2022-08-17 14:19 ` Richard Earnshaw [this message]
2022-08-17 20:22 ` Jonathan Wakely
2022-09-04 17:25 ` Aaron Gray
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=8333c102-ac9c-1a31-c500-8ac042b960d3@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=aaronngray.lists@gmail.com \
--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).