Re: [RFC] Closing of all remaining Bugzilla PRs against powerpcspe

2020-06-02 Thread Segher Boessenkool
Hi Arseny, On Mon, Jun 01, 2020 at 10:38:16AM +0700, Arseny Solokha wrote: > > PRs from the second group were filed by me, so if there's consensus to > > close all > > of them, the ones from this second group I can close myself. I don't > > have the > > right permissions to m

Re: sign_and_send_pubkey: signing failed: agent refused operation

2020-06-02 Thread Martin Sebor via Gcc
On 6/2/20 2:43 PM, Jonathan Wakely wrote: On Tue, 2 Jun 2020 at 21:26, Martin Sebor wrote: On 6/1/20 1:12 PM, Jonathan Wakely via Overseers wrote: On Mon, 1 Jun 2020 at 19:11, Frank Ch. Eigler via Gcc wrote: Hi - git pull from the GCC and Glibc repos is failing for me with the error belo

Re: sign_and_send_pubkey: signing failed: agent refused operation

2020-06-02 Thread Jonathan Wakely via Gcc
On Tue, 2 Jun 2020 at 21:26, Martin Sebor wrote: > > On 6/1/20 1:12 PM, Jonathan Wakely via Overseers wrote: > > On Mon, 1 Jun 2020 at 19:11, Frank Ch. Eigler via Gcc > > wrote: > >> > >> Hi - > >> > >>> git pull from the GCC and Glibc repos is failing for me with the error > >>> below. It work

Re: sign_and_send_pubkey: signing failed: agent refused operation

2020-06-02 Thread Martin Sebor via Gcc
On 6/1/20 1:12 PM, Jonathan Wakely via Overseers wrote: On Mon, 1 Jun 2020 at 19:11, Frank Ch. Eigler via Gcc wrote: Hi - git pull from the GCC and Glibc repos is failing for me with the error below. It worked fine last week and I haven't made any changes to my ssh keys. And are you loggi

Re: sign_and_send_pubkey: signing failed: agent refused operation

2020-06-02 Thread Jim Wilson
On Mon, Jun 1, 2020 at 3:33 PM Martin Sebor via Gcc wrote: > So it sounds like you wouldn't expect the "agent refused operation" > error either, and it's not just a poor error message that I should > learn to live with. That makes me think I should try to figure out > what's wrong. I think the ~

Re: [IMPORTANT] ChangeLog related changes

2020-06-02 Thread Martin Liška
On 6/2/20 4:14 PM, Jonathan Wakely wrote: On Tue, 2 Jun 2020 at 14:56, Jonathan Wakely wrote: On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote: On 6/2/20 1:48 PM, Martin Liška wrote: I tend to this approach. Let me prepare a patch candidate for it. There's a patch for it. Can you please J

Re: [IMPORTANT] ChangeLog related changes

2020-06-02 Thread Jonathan Wakely via Gcc
On Tue, 2 Jun 2020 at 14:56, Jonathan Wakely wrote: > > On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote: > > > > On 6/2/20 1:48 PM, Martin Liška wrote: > > > I tend to this approach. Let me prepare a patch candidate for it. > > > > There's a patch for it. Can you please Jonathan take a look? > >

Re: [IMPORTANT] ChangeLog related changes

2020-06-02 Thread Martin Liška
On 6/2/20 3:56 PM, Jonathan Wakely wrote: On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote: On 6/2/20 1:48 PM, Martin Liška wrote: I tend to this approach. Let me prepare a patch candidate for it. There's a patch for it. Can you please Jonathan take a look? Looks great, thanks! +

Re: [IMPORTANT] ChangeLog related changes

2020-06-02 Thread Jonathan Wakely via Gcc
On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote: > > On 6/2/20 1:48 PM, Martin Liška wrote: > > I tend to this approach. Let me prepare a patch candidate for it. > > There's a patch for it. Can you please Jonathan take a look? Looks great, thanks! +if name not in wildcard_prefixe

Re: [IMPORTANT] ChangeLog related changes

2020-06-02 Thread Martin Liška
On 6/2/20 1:48 PM, Martin Liška wrote: I tend to this approach. Let me prepare a patch candidate for it. There's a patch for it. Can you please Jonathan take a look? Thanks, Martin >From 4d2cf31b6deb03c9ddc8062b9a45d2511e4a58bb Mon Sep 17 00:00:00 2001 From: Martin Liska Date: Tue, 2 Jun 2020

Re: [IMPORTANT] ChangeLog related changes

2020-06-02 Thread Martin Liška
On 6/2/20 1:22 PM, Jonathan Wakely via Gcc-patches wrote: On Tue, 2 Jun 2020 at 12:09, Jonathan Wakely wrote: On Tue, 2 Jun 2020 at 12:05, Jonathan Wakely wrote: On Tue, 2 Jun 2020 at 11:56, Gerald Pfeifer wrote: On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote: The libstdc++ m

Re: [IMPORTANT] ChangeLog related changes

2020-06-02 Thread Jonathan Wakely via Gcc
On Tue, 2 Jun 2020 at 12:09, Jonathan Wakely wrote: > > On Tue, 2 Jun 2020 at 12:05, Jonathan Wakely wrote: > > > > On Tue, 2 Jun 2020 at 11:56, Gerald Pfeifer wrote: > > > > > > On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote: > > > > The libstdc++ manual is written in Docbook XML, bu

Re: [IMPORTANT] ChangeLog related changes

2020-06-02 Thread Jonathan Wakely via Gcc
On Tue, 2 Jun 2020 at 12:05, Jonathan Wakely wrote: > > On Tue, 2 Jun 2020 at 11:56, Gerald Pfeifer wrote: > > > > On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote: > > > The libstdc++ manual is written in Docbook XML, but we commit both the > > > XML and generated HTML pages to Git. Som

Re: [IMPORTANT] ChangeLog related changes

2020-06-02 Thread Jonathan Wakely via Gcc
On Tue, 2 Jun 2020 at 07:44, Martin Liška wrote: > > On 6/1/20 7:24 PM, Jonathan Wakely wrote: > > On Mon, 25 May 2020 at 23:50, Jakub Jelinek via Gcc wrote: > >> > >> Hi! > >> > >> I've turned the strict mode of Martin Liška's hook changes, > >> which means that from now on no commits to the tru

Re: [IMPORTANT] ChangeLog related changes

2020-06-02 Thread Jonathan Wakely via Gcc
On Tue, 2 Jun 2020 at 11:56, Gerald Pfeifer wrote: > > On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote: > > The libstdc++ manual is written in Docbook XML, but we commit both the > > XML and generated HTML pages to Git. Sometimes a small XML file can > > result in dozens of mechanical ch

Re: [IMPORTANT] ChangeLog related changes

2020-06-02 Thread Gerald Pfeifer
On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote: > The libstdc++ manual is written in Docbook XML, but we commit both the > XML and generated HTML pages to Git. Sometimes a small XML file can > result in dozens of mechanical changes to the generated HTML files, > which we record in the Ch

Re: [1-800-GIT-HELP] Backporting a series of commits into a combined commit?

2020-06-02 Thread Martin Liška
On 6/2/20 11:01 AM, Jakub Jelinek wrote: On Tue, Jun 02, 2020 at 10:53:57AM +0200, Richard Biener wrote: On Mon, Jun 1, 2020 at 2:17 PM Thomas Koenig via Fortran wrote: Hi Martin, For now, I would recommend doing 1:1 backports. Otherwise, you'll need to merge all ChangeLog entries in a form

Re: [1-800-GIT-HELP] Backporting a series of commits into a combined commit?

2020-06-02 Thread Jakub Jelinek via Gcc
On Tue, Jun 02, 2020 at 10:53:57AM +0200, Richard Biener wrote: > On Mon, Jun 1, 2020 at 2:17 PM Thomas Koenig via Fortran > wrote: > > > > Hi Martin, > > > > > For now, I would recommend doing 1:1 backports. Otherwise, you'll need > > > to merge > > > all ChangeLog entries in a format the server

Re: [1-800-GIT-HELP] Backporting a series of commits into a combined commit?

2020-06-02 Thread Richard Biener via Gcc
On Mon, Jun 1, 2020 at 2:17 PM Thomas Koenig via Fortran wrote: > > Hi Martin, > > > For now, I would recommend doing 1:1 backports. Otherwise, you'll need > > to merge > > all ChangeLog entries in a format the server hook accepts. That can > > require some > > work. > > If the first commit caused