Thanks both!
Cheers,
Tamar
> -Original Message-
> From: Martin Liška
> Sent: Wednesday, June 10, 2020 2:41 PM
> To: Tamar Christina ; Jonathan Wakely
>
> Cc: Jakub Jelinek ; gcc@gcc.gnu.org; gcc-patches patc...@gcc.gnu.org>
> Subject: Re: [IMPORTANT] ChangeLog
How do we handle multi author patches nowadays?
Tried searching for it on the website but couldn’t find anything.
Thanks,
Tamar
-Original Message-
From: Gcc-patches On Behalf Of Martin
Liška
Sent: Wednesday, June 10, 2020 8:38 AM
To: Jonathan Wakely
Cc: Jakub Jelinek ; gcc@gcc.g
On Wed, Jun 10, 2020 at 01:34:54PM +, Tamar Christina wrote:
> Hi All,
>
> We've been wondering since we no longer list authors in the changelog (at
> least mklog doesn't generate it),
> How do we handle multi author patches nowadays?
>
> Tried searching for it on the website but couldn’t fi
rom: Gcc-patches On Behalf Of Martin
> Liška
> Sent: Wednesday, June 10, 2020 8:38 AM
> To: Jonathan Wakely
> Cc: Jakub Jelinek ; gcc@gcc.gnu.org; gcc-patches patc...@gcc.gnu.org>
> Subject: Re: [IMPORTANT] ChangeLog related changes
>
> On 6/9/20 10:29 PM, Jonathan Wakely
On 6/9/20 10:29 PM, Jonathan Wakely wrote:
OK, here's a proper patch for the changes you liked, dropping the
changes to the Error exception type.
pytest contrib/gcc-changelog/test_email.py passes.
OK for master?
I like it and I've just pushed the patch to master.
Martin
On Tue, 2 Jun 2020 at 15:25, Martin Liška wrote:
>
> 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
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
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?
>
>
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!
+
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
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
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
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
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
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
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
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
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 trunk or release branches
should be changing any ChangeLog files together with th
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 trunk or release branches
> should be changing any ChangeLog files together with the other files,
> ChangeLog entry sh
On 5/31/20 10:27 PM, Segher Boessenkool wrote:
On Tue, May 26, 2020 at 03:14:02PM +0200, Andreas Schwab wrote:
On Mai 26 2020, Martin Liška wrote:
subprocess.check_output('git show --name-only --pretty="" | '
'grep ChangeLog | '
git show --name-only
On Tue, May 26, 2020 at 03:14:02PM +0200, Andreas Schwab wrote:
> On Mai 26 2020, Martin Liška wrote:
>
> > subprocess.check_output('git show --name-only --pretty="" | '
> > 'grep ChangeLog | '
>
> git show --name-only --pretty= -- '*ChangeLog*'
Or even ju
Hi Jakub,
On Tue, May 26, 2020 at 12:42:41PM +0200, Thomas Koenig wrote:
So, two questions:
- How do I get my gcc-10 branch back into a consistent state?
That works, thanks.
git reset --hard origin/releases/gcc-10
should do it (if you want to throw all your local changes).
- How are ba
On 5/26/20 3:14 PM, Andreas Schwab wrote:
-- '*ChangeLog*'
Thank you for the comment.
There's a proper patch for 'git gcc-backport' alias.
Thoughts?
Martin
>From a1511dd6ccda73befe3282c43671a6c4623d5d7d Mon Sep 17 00:00:00 2001
From: Martin Liska
Date: Tue, 26 May 2020 15:32:32 +0200
Subject
On Mai 26 2020, Martin Liška wrote:
> subprocess.check_output('git show --name-only --pretty="" | '
> 'grep ChangeLog | '
git show --name-only --pretty= -- '*ChangeLog*'
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4
On 5/26/20 1:34 PM, Jakub Jelinek via Gcc wrote:
On Tue, May 26, 2020 at 12:27:59PM +0100, Richard Earnshaw wrote:
I haven't investigated in detail, but could we use a merge strategy with
the cherry-pick to drop ChangeLog entries?
If that works, sure.
Note, when cherry-picking commits from bef
On Tue, May 26, 2020 at 12:27:59PM +0100, Richard Earnshaw wrote:
> I haven't investigated in detail, but could we use a merge strategy with
> the cherry-pick to drop ChangeLog entries?
If that works, sure.
Note, when cherry-picking commits from before conversion to git or whenever
people started
On 26/05/2020 12:19, Jakub Jelinek via Gcc wrote:
> On Tue, May 26, 2020 at 12:42:41PM +0200, Thomas Koenig wrote:
>> Am 26.05.20 um 11:04 schrieb Thomas Koenig via Gcc:
>>> Am 26.05.20 um 00:48 schrieb Jakub Jelinek via Gcc:
>>>
I've turned the strict mode of Martin Liška's hook changes,
>>>
On Tue, May 26, 2020 at 12:42:41PM +0200, Thomas Koenig wrote:
> Am 26.05.20 um 11:04 schrieb Thomas Koenig via Gcc:
> > Am 26.05.20 um 00:48 schrieb Jakub Jelinek via Gcc:
> >
> > > I've turned the strict mode of Martin Liška's hook changes,
> >
> > This means that it is no longer possible to do
Am 26.05.20 um 11:04 schrieb Thomas Koenig via Gcc:
Am 26.05.20 um 00:48 schrieb Jakub Jelinek via Gcc:
I've turned the strict mode of Martin Liška's hook changes,
This means that it is no longer possible to do a git gcc-backport
[CC'ing fortran to warn other people against currently trying
Am 26.05.20 um 00:48 schrieb Jakub Jelinek via Gcc:
I've turned the strict mode of Martin Liška's hook changes,
This means that it is no longer possible to do a git gcc-backport
followed by a git push. If there is a procedure for this, it
is not documented on https://gcc.gnu.org/gitwrite.html
Great, thanks!
On Tue, May 26, 2020 at 2:08 PM Martin Liška wrote:
>
> On 5/26/20 7:22 AM, Hongtao Liu via Gcc wrote:
> > i commit a separate patch alone only for ChangeLog files, should i revert
> > it?
>
> Hello.
>
> I've just done it.
>
> Martin
--
BR,
Hongtao
On 5/26/20 7:22 AM, Hongtao Liu via Gcc wrote:
i commit a separate patch alone only for ChangeLog files, should i revert it?
Hello.
I've just done it.
Martin
On Tue, May 26, 2020 at 6:49 AM Jakub Jelinek via Gcc-patches
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 trunk or release branches
> should be changing any ChangeLog files together with the other files,
> ChangeLo
Hi!
I've turned the strict mode of Martin Liška's hook changes,
which means that from now on no commits to the trunk or release branches
should be changing any ChangeLog files together with the other files,
ChangeLog entry should be solely in the commit message.
The DATESTAMP bumping script will b
34 matches
Mail list logo
