Snapshot gcc-9-20200118 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/9-20200118/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Le 18/01/2020 à 18:49, Segher Boessenkool a écrit :
On Wed, Jan 15, 2020 at 04:37:49PM +, Iain Sandoe wrote:
I’m guessing that public development branches will probably gravitate to the
no non-FF mode, if they are to be used by people other than the primary author
.. although that does some
On Wed, Jan 15, 2020 at 04:37:49PM +, Iain Sandoe wrote:
> I’m guessing that public development branches will probably gravitate to the
> no non-FF mode, if they are to be used by people other than the primary author
>
> .. although that does somewhat limit things; rebasing WIP onto trunk and
TL;DR: See subject. Verbosity follows.
The git transition is mostly for the better. Thanks to those
investing time and effort. There's always fallout. Here's one
dustcloud:
In the distant past with svn, there messages to gcc-cvs@ were
somewhat like git show --stat, i.e. without the actual cha
[ gcc-patches -> gcc ]
On Sat, 18 Jan 2020, Gerald Pfeifer wrote:
> Remove all references how to perform local checkouts, to SVN, and
> mirroring the repository. Instead generalize descriptions since
> with the move to Git syncing the repository with rsync and then
> checking out locally became m
All (annotated) release tags are misnamed. For example,
refs/tags/releases/gcc-9.2.0 is really named gcc_9_2_0_release:
$ git cat-file -p releases/gcc-9.2.0
object a0c06cc27d2146b7d86758ffa236516c6143d62c
type commit
tag gcc_9_2_0_release
tagger Jakub Jelinek 1565595539 +020
