On Freitag, 24. Januar 2020 04:38:48 CET Nicholas Krause wrote:
> On 1/23/20 12:19 PM, Nicholas Krause wrote:
> > On 1/23/20 3:39 AM, Allan Sandfeld Jensen wrote:
> >> On Montag, 20. Januar 2020 20:26:46 CET Nicholas Krause wrote:
> >>> Greetings All,
> >>>
> >>> Unfortunately due to me being rath
On Fri, 24 Jan 2020 at 03:39, Nicholas Krause wrote:
> Sorry for the second message Allan but make -j does not scale well
> beyond 4 or
> 8 threads and that's considering a 4 core or 8 machine. The problem has to
> do with large build machines with CPUs with more cores than this or as
> is becomin
On Thu, 23 Jan 2020 at 23:15, Peter Bergner wrote:
>
> On 1/23/20 12:09 PM, Peter Bergner wrote:
> > On 1/23/20 4:29 AM, Jakub Jelinek wrote:
> >> so it is not a fast forward merge and we have the requirement that
> >> From-SVN: shouldn't appear in commit logs of new commits.
> >
> > So I just did
On 23/01/20 16:23 +, Richard Earnshaw (lists) wrote:
On 21/01/2020 18:58, Richard Earnshaw (lists) wrote:
This patch documents some of the scripts that I've published for
managing the personal and vendor spaces on the server. It also
covers some of the other features that those scripts ena
On Thu, 23 Jan 2020 at 16:57, Andrew Stubbs wrote:
> Indeed, PR2019 has a number of unrelated commits referenced, and pr2018
> has one too. The years before that appear to have escaped the problem.
The 2019 ones are even more silly, as the unrelated commits were
correcting the PR number in some fi
On 24/01/2020 11:04, Jonathan Wakely wrote:
On 23/01/20 16:23 +, Richard Earnshaw (lists) wrote:
On 21/01/2020 18:58, Richard Earnshaw (lists) wrote:
This patch documents some of the scripts that I've published for
managing the personal and vendor spaces on the server. It also
covers some
On 24/01/20 11:48 +, Richard Earnshaw (lists) wrote:
On 24/01/2020 11:04, Jonathan Wakely wrote:
On 23/01/20 16:23 +, Richard Earnshaw (lists) wrote:
On 21/01/2020 18:58, Richard Earnshaw (lists) wrote:
This patch documents some of the scripts that I've published for
managing the perso
On 24/01/2020 12:19, Jonathan Wakely wrote:
On 24/01/20 11:48 +, Richard Earnshaw (lists) wrote:
On 24/01/2020 11:04, Jonathan Wakely wrote:
On 23/01/20 16:23 +, Richard Earnshaw (lists) wrote:
On 21/01/2020 18:58, Richard Earnshaw (lists) wrote:
This patch documents some of the script
On 24/01/20 13:55 +, Richard Earnshaw (lists) wrote:
On 24/01/2020 12:19, Jonathan Wakely wrote:
On 24/01/20 11:48 +, Richard Earnshaw (lists) wrote:
On 24/01/2020 11:04, Jonathan Wakely wrote:
On 23/01/20 16:23 +, Richard Earnshaw (lists) wrote:
On 21/01/2020 18:58, Richard Earns
On 24/01/20 15:09 +, Jonathan Wakely wrote:
On 24/01/20 13:55 +, Richard Earnshaw (lists) wrote:
On 24/01/2020 12:19, Jonathan Wakely wrote:
On 24/01/20 11:48 +, Richard Earnshaw (lists) wrote:
On 24/01/2020 11:04, Jonathan Wakely wrote:
On 23/01/20 16:23 +, Richard Earnshaw (
On 24/01/2020 15:12, Jonathan Wakely wrote:
On 24/01/20 15:09 +, Jonathan Wakely wrote:
On 24/01/20 13:55 +, Richard Earnshaw (lists) wrote:
On 24/01/2020 12:19, Jonathan Wakely wrote:
On 24/01/20 11:48 +, Richard Earnshaw (lists) wrote:
On 24/01/2020 11:04, Jonathan Wakely wrote:
On 1/24/20 3:18 AM, Allan Sandfeld Jensen wrote:
On Freitag, 24. Januar 2020 04:38:48 CET Nicholas Krause wrote:
On 1/23/20 12:19 PM, Nicholas Krause wrote:
On 1/23/20 3:39 AM, Allan Sandfeld Jensen wrote:
On Montag, 20. Januar 2020 20:26:46 CET Nicholas Krause wrote:
Greetings All,
Unfor
On 24/01/2020 10:27, Jonathan Wakely wrote:
On Fri, 24 Jan 2020 at 03:39, Nicholas Krause wrote:
Sorry for the second message Allan but make -j does not scale well
beyond 4 or
8 threads and that's considering a 4 core or 8 machine. The problem has to
do with large build machines with CPUs with
On Freitag, 24. Januar 2020 17:29:06 CET Nicholas Krause wrote:
> On 1/24/20 3:18 AM, Allan Sandfeld Jensen wrote:
> > On Freitag, 24. Januar 2020 04:38:48 CET Nicholas Krause wrote:
> >> On 1/23/20 12:19 PM, Nicholas Krause wrote:
> >>> On 1/23/20 3:39 AM, Allan Sandfeld Jensen wrote:
> On Mo
On 1/24/20 1:28 PM, Allan Sandfeld Jensen wrote:
On Freitag, 24. Januar 2020 17:29:06 CET Nicholas Krause wrote:
On 1/24/20 3:18 AM, Allan Sandfeld Jensen wrote:
On Freitag, 24. Januar 2020 04:38:48 CET Nicholas Krause wrote:
On 1/23/20 12:19 PM, Nicholas Krause wrote:
On 1/23/20 3:39 AM,
>> > On 1/24/20 8:45 AM, David Edelsohn wrote:
>> > > There is no ChangeLog entry for the testsuite changes.
>> >
>> > I don't believe in ChangeLog entries for testcases, but I'll add one for
>> > the target-supports.exp change, thanks.
>>
>> Is this a general policy change that we want to make? C
On Fri, 2020-01-24 at 13:49 -0500, David Edelsohn wrote:
> > > > On 1/24/20 8:45 AM, David Edelsohn wrote:
> > > > > There is no ChangeLog entry for the testsuite changes.
> > > >
> > > > I don't believe in ChangeLog entries for testcases, but I'll add one for
> > > > the target-supports.exp chang
> I strongly prefer to move towards relying on the git log.
In my experience the output of git log is a total mess so cannot replace
ChangeLogs. But we can well decide to drop ChangeLog for the testsuite.
--
Eric Botcazou
* Eric Botcazou:
>> I strongly prefer to move towards relying on the git log.
>
> In my experience the output of git log is a total mess so cannot replace
> ChangeLogs.
That's fixable if the commit message is part of the patch review
(just like the source code comments).
On Fri, 2020-01-24 at 20:32 +0100, Eric Botcazou wrote:
> > I strongly prefer to move towards relying on the git log.
>
> In my experience the output of git log is a total mess so cannot replace
> ChangeLogs. But we can well decide to drop ChangeLog for the testsuite.
Well, glibc has moved to ex
On Fri, Jan 24, 2020 at 02:36:31PM -0700, Jeff Law wrote:
> On Fri, 2020-01-24 at 20:32 +0100, Eric Botcazou wrote:
> > > I strongly prefer to move towards relying on the git log.
> >
> > In my experience the output of git log is a total mess so cannot replace
> > ChangeLogs. But we can well dec
On Fri, 2020-01-24 at 22:45 +0100, Jakub Jelinek wrote:
> > > In my experience the output of git log is a total mess so cannot
> > > replace ChangeLogs. But we can well decide to drop ChangeLog for
> > > the testsuite.
> >
> > Well, glibc has moved to extracting them from git, building
> > polici
Snapshot gcc-8-20200124 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/8-20200124/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Fri, Jan 24, 2020 at 2:39 PM Paul Smith wrote:
>
> On Fri, 2020-01-24 at 22:45 +0100, Jakub Jelinek wrote:
> > > > In my experience the output of git log is a total mess so cannot
> > > > replace ChangeLogs. But we can well decide to drop ChangeLog for
> > > > the testsuite.
> > >
> > > Well,
24 matches
Mail list logo
