Re: [PATCH v4 0/8] Fix gdb.base/gdb-sigterm.exp failure/error

Kevin Buettner via Gdb-patches
2023-01-27T22:04:21Z

On Thu, 12 Jan 2023 13:37:00 +0100
Tom de Vries <tdevries@suse.de> wrote:

> FWIW, I ran into this when applying:
> ...
> $ git am ~/patches/grouped/eml/*
> Applying: Introduce gdb_exception_forced_quit
> Applying: Handle gdb SIGTERM by throwing / catching gdb_exception_force_quit
> .git/rebase-apply/patch:37: indent with spaces.
> {
> warning: 1 line adds whitespace errors.
> Applying: Catch gdb_exception_error instead of gdb_exception (in many
> places)
> Applying: Python QUIT processing updates
> Applying: Guile QUIT processing updates
> Applying: Call quit_force for gdb_exception_forced_quit in
> safe_execute_command
> Applying: QUIT processing w/ explicit throw for gdb_exception_forced_quit
> .git/rebase-apply/patch:17: indent with spaces.
> throw;
> .git/rebase-apply/patch:46: indent with spaces.
> {
> .git/rebase-apply/patch:58: indent with spaces.
> {
> warning: 3 lines add whitespace errors.
> Applying: Forced quit cases handled by resetting sync_quit_force_run
> .git/rebase-apply/patch:41: indent with spaces.
> to newline, so, for this case, reset the quit flag for
> warning: 1 line adds whitespace errors.
> ...

Thanks!

I've fixed these whitespace problems in my local sources. I've
also added a "Tested-by" attribution for you to each commit message.

Kevin