On 12/05/2020 10:05, Martin Liška wrote:
> Hi.
>
> Thanks to Jakub, we finally set up an experimental environment:
> gcc.gnu.org/home/gccadmin/gcc-reposurgeon-8.git
>
> The repository now contains a new pre-commit hook that validates
> the git commit format ([1]) and provides a reasonable error m
On 5/13/20 11:50 AM, Jozef Lawrynowicz wrote:
"git_changelog.py" is nowhere to be found in the gcc-changelog or
gcc-reposurgeon-8 repos. Is it equivalent to any of the other scripts in
gcc-changelog?
Yes, I made some refactoring and I'm going to send a proper gcc-patches
submission.
The script
On 5/13/20 11:29 AM, Richard Biener wrote:
Hmm, it's OK in the commit but it should be omitted in the
ChangeLog files.
No, ChangeLog file identification should not be prepended
with a tab.
"testsuite/" will work.
Martin
Hi,
On Tue, 12 May 2020 11:05:58 +0200
Martin Liška wrote:
> Hi.
>
> Thanks to Jakub, we finally set up an experimental environment:
> gcc.gnu.org/home/gccadmin/gcc-reposurgeon-8.git
>
> The repository now contains a new pre-commit hook that validates
> the git commit format ([1]) and provides
On Wed, May 13, 2020 at 11:27 AM Martin Liška wrote:
>
> On 5/13/20 10:16 AM, Richard Sandiford wrote:
> > As far as this particular example goes, shouldn't the "testsuite/" line
> > be dropped from the above?
>
> Good point. Fixes now with:
>
> $ ./git_email.py
> patches/0020-IPA-Avoid-segfault-
Hi Martin,
Thanks to Jakub, we finally set up an experimental environment:
gcc.gnu.org/home/gccadmin/gcc-reposurgeon-8.git
How does one go about testing this? It would be helpful if you
could explain this assuming that the Fortran people have at best
an extremely shallow knowledge of git and
On 5/13/20 10:16 AM, Richard Sandiford wrote:
As far as this particular example goes, shouldn't the "testsuite/" line
be dropped from the above?
Good point. Fixes now with:
$ ./git_email.py
patches/0020-IPA-Avoid-segfault-in-devirtualization_time_bonus-PR.patch
Errors:
first line should start
Martin Liška writes:
> Hi.
>
> Thanks to Jakub, we finally set up an experimental environment:
> gcc.gnu.org/home/gccadmin/gcc-reposurgeon-8.git
>
> The repository now contains a new pre-commit hook that validates
> the git commit format ([1]) and provides a reasonable error message
> when violate
On Tue, May 12, 2020 at 11:05:58AM +0200, Martin Liška wrote:
> Thanks to Jakub, we finally set up an experimental environment:
> gcc.gnu.org/home/gccadmin/gcc-reposurgeon-8.git
>
> The repository now contains a new pre-commit hook that validates
> the git commit format ([1]) and provides a reason
I'm also CCing gcc-patches and fortran ML.
Martin
On 5/12/20 11:05 AM, Martin Liška wrote:
Hi.
Thanks to Jakub, we finally set up an experimental environment:
gcc.gnu.org/home/gccadmin/gcc-reposurgeon-8.git
The repository now contains a new pre-commit hook that validates
the git commit format
Hi.
Thanks to Jakub, we finally set up an experimental environment:
gcc.gnu.org/home/gccadmin/gcc-reposurgeon-8.git
The repository now contains a new pre-commit hook that validates
the git commit format ([1]) and provides a reasonable error message
when violated. The hook is based on [2] and the
11 matches
Mail list logo
