public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org, pedro@palves.net
Subject: Re: [PATCH v4 0/8] Fix gdb.base/gdb-sigterm.exp failure/error
Date: Fri, 27 Jan 2023 15:03:56 -0700	[thread overview]
Message-ID: <20230127150356.0cd024c2@f37-zws-1> (raw)
In-Reply-To: <939427f4-8b1f-1230-78d9-85d3aa3d7ac5@suse.de>

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


      reply	other threads:[~2023-01-27 22:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  1:56 Kevin Buettner
2023-01-12  1:56 ` [PATCH v4 1/8] Introduce gdb_exception_forced_quit Kevin Buettner
2023-01-30 18:56   ` Pedro Alves
2023-01-12  1:56 ` [PATCH v4 2/8] Handle gdb SIGTERM by throwing / catching gdb_exception_force_quit Kevin Buettner
2023-01-30 18:57   ` Pedro Alves
2023-01-12  1:56 ` [PATCH v4 3/8] Catch gdb_exception_error instead of gdb_exception (in many places) Kevin Buettner
2023-01-30 19:00   ` Pedro Alves
2023-02-16 10:52     ` Pedro Alves
2023-01-12  1:56 ` [PATCH v4 4/8] Python QUIT processing updates Kevin Buettner
2023-01-30 19:01   ` Pedro Alves
2023-02-20  2:52     ` Kevin Buettner
2023-02-23 12:50       ` Pedro Alves
2023-01-12  1:56 ` [PATCH v4 5/8] Guile " Kevin Buettner
2023-01-12  1:56 ` [PATCH v4 6/8] Call quit_force for gdb_exception_forced_quit in safe_execute_command Kevin Buettner
2023-01-30 19:01   ` Pedro Alves
2023-01-12  1:56 ` [PATCH v4 7/8] QUIT processing w/ explicit throw for gdb_exception_forced_quit Kevin Buettner
2023-01-30 19:02   ` Pedro Alves
2023-01-12  1:56 ` [PATCH v4 8/8] Forced quit cases handled by resetting sync_quit_force_run Kevin Buettner
2023-01-30 19:02   ` Pedro Alves
2023-01-12 12:37 ` [PATCH v4 0/8] Fix gdb.base/gdb-sigterm.exp failure/error Tom de Vries
2023-01-27 22:03   ` Kevin Buettner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230127150356.0cd024c2@f37-zws-1 \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    --cc=tdevries@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).