From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
Jonathan Wakely via Fortran <fortran@gcc.gnu.org>,
Wileam Yonatan Phan <wileamyp@outlook.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GSoC Blog Post 0 - GCCprefab build system
Date: Sat, 18 Jun 2022 21:24:15 +0200 [thread overview]
Message-ID: <C0EC3007-EEF7-4197-B822-781DD9701501@gmail.com> (raw)
In-Reply-To: <YqzcQ7FDIgnqKPAZ@tucnak>
On 17 June 2022 21:55:47 CEST, Jakub Jelinek <jakub@redhat.com> wrote:
>On Fri, Jun 17, 2022 at 08:45:04PM +0200, Bernhard Reutner-Fischer via Gcc wrote:
>> PS: we should rm https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=contrib/gcc_build
>
>No. gcc_build is used by maintainer-scripts/gcc_release, so by killing it
>you'd make gcc unreleasable.
Doh, didn't grep in maintainer-scripts.
So, should the SVN parts be ripped out?
For non-maintainers, switch it to git instead?
>> It was not updated since the switch to git so, apparently, nobody uses it anymore (sadly, seeing who authored it).
The hunks talking about subversion do seem to be misleading nowadays, aren't they?
thanks,
next prev parent reply other threads:[~2022-06-18 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 1:50 Wileam Yonatan Phan
2022-06-13 11:59 ` Jonathan Wakely
2022-06-13 13:34 ` Wileam Yonatan Phan
2022-06-13 15:26 ` Jonathan Wakely
2022-06-13 17:12 ` Wileam Yonatan Phan
2022-06-13 17:38 ` Jonathan Wakely
2022-06-14 0:37 ` Damian Rouson
2022-06-14 8:53 ` Jonathan Wakely
2022-06-14 11:16 ` Damian Rouson
2022-06-14 13:52 ` Wileam Yonatan Phan
2022-06-17 18:45 ` Bernhard Reutner-Fischer
2022-06-17 19:55 ` Jakub Jelinek
2022-06-18 19:24 ` Bernhard Reutner-Fischer [this message]
2022-06-17 20:07 ` Jonathan Wakely
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=C0EC3007-EEF7-4197-B822-781DD9701501@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jwakely.gcc@gmail.com \
--cc=wileamyp@outlook.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).