Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hannes Domani <ssbssa@yahoo.de>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	 Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH v2 04/11] Create x86-windows-nat.c
Date: Sat, 17 Jan 2026 15:15:15 +0000 (UTC)	[thread overview]
Message-ID: <1598131329.2278982.1768662915270@mail.yahoo.com> (raw)
In-Reply-To: <b3fc2327-2379-4a79-abe2-f07d72924073@simark.ca>

 Am Samstag, 17. Januar 2026 um 16:05:00 MEZ hat Simon Marchi <simark@simark.ca> Folgendes geschrieben:

> On 2026-01-17 09:01, Hannes Domani wrote:
> >  Am Samstag, 17. Januar 2026 um 14:56:45 MEZ hat Hannes Domani <ssbssa@yahoo.de> Folgendes geschrieben:
> >
> >> Also creates the x86_windows_per_inferior and x86_windows_nat_target
> >> derived classes in there which will then hold the arch-specific data and
> >> function overrides.
> >> ---
> >> gdb/Makefile.in      |  1 +
> >> gdb/configure.nat    | 12 ++++++++----
> >> gdb/windows-nat.c    |  7 +------
> >> gdb/x86-windows-nat.c | 42 ++++++++++++++++++++++++++++++++++++++++++
> >> 4 files changed, 52 insertions(+), 10 deletions(-)
> >> create mode 100644 gdb/x86-windows-nat.c
> >
> > I'm sorry about these duplicate mails.
> >
> > When I first used git send-email, it only succeeded for 10 of the 11 patches.
> > So I tried again, and since it asks me for each patch individually if
> > I want to send it, I thought I could use that to only send patch 11 again.
> > But for some reason it didn't ask me for some of them, and just sent
> > these duplicates.
> >
> > Is there a correct way to do this?
> 
> Not sure if this is what happened to you, but my mail provider only accepts
> up to about X messages in short span of time (I don't remember the exact
> value of X, but it's around 10).  Did the server respond with some
> rejection status code/message for the last message?

I only got this message:
6.6.0 Error sending message for delivery.

But I guess my mail provider has a similar limit.


> I have these settings in my git config to work around this:
> 
> 
> [sendemail]
> 
>         smtpReloginDelay = 120
>         smtpBatchSize = 8
> 
> This means that git-send-email will send up to 8 messages in a given
> session.  After 8, it will wait 120 seconds and do a fresh login to
> continue.

I added this to my git config, thanks.


Hannes

  reply	other threads:[~2026-01-17 15:15 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260117134052.2660009-1-ssbssa.ref@yahoo.de>
2026-01-17 13:36 ` [PATCH v2 01/11] Remove duplicate code from windows_nat_target::resume Hannes Domani
2026-01-17 13:36   ` [PATCH v2 02/11] Simplify windows_nat_target::resume Hannes Domani
2026-01-19 13:55     ` Schimpe, Christina
2026-01-21 15:42       ` Tom Tromey
2026-01-23 19:11       ` Hannes Domani
2026-01-17 13:36   ` [PATCH v2 03/11] Move struct declarations into windows-nat.h Hannes Domani
2026-01-17 13:36   ` [PATCH v2 04/11] Create x86-windows-nat.c Hannes Domani
2026-01-21 15:38     ` Tom Tromey
2026-01-17 13:36   ` [PATCH v2 05/11] Move x86 debug registers and related code into x86-windows-nat.c Hannes Domani
2026-01-19 12:49     ` Schimpe, Christina
2026-01-20 15:49       ` Hannes Domani
2026-01-21  8:06         ` Schimpe, Christina
2026-01-23 13:17     ` [PATCH v3] " Hannes Domani
2026-01-23 18:50       ` Tom Tromey
2026-01-23 19:20         ` Hannes Domani
2026-01-23 19:56           ` Tom Tromey
2026-01-17 13:36   ` [PATCH v2 06/11] Move x86 register " Hannes Domani
2026-01-19 12:50     ` Schimpe, Christina
2026-01-17 13:36   ` [PATCH v2 07/11] Move x86 selector " Hannes Domani
2026-01-19 13:56     ` Schimpe, Christina
2026-01-17 13:36   ` [PATCH v2 08/11] Move software breakpoint recognition " Hannes Domani
2026-01-19 12:51     ` Schimpe, Christina
2026-01-21 15:43       ` Tom Tromey
2026-01-23 19:12         ` Hannes Domani
2026-01-17 13:36   ` [PATCH v2 09/11] Move auto_wide_charset gdbarch method to windows-tdep Hannes Domani
2026-01-17 13:36   ` [PATCH v2 10/11] Move setting size of long " Hannes Domani
2026-01-21 15:47     ` Tom Tromey
2026-01-17 13:54   ` [PATCH v2 04/11] Create x86-windows-nat.c Hannes Domani
2026-01-17 14:01     ` Hannes Domani
2026-01-17 14:14       ` Hannes Domani
2026-01-17 15:04       ` Simon Marchi
2026-01-17 15:15         ` Hannes Domani [this message]
2026-01-17 13:54   ` [PATCH v2 05/11] Move x86 debug registers and related code into x86-windows-nat.c Hannes Domani
2026-01-17 13:54   ` [PATCH v2 06/11] Move x86 register " Hannes Domani
2026-01-21 16:08     ` Tom Tromey
2026-01-17 13:54   ` [PATCH v2 09/11] Move auto_wide_charset gdbarch method to windows-tdep Hannes Domani
2026-01-21 15:48     ` Tom Tromey
2026-01-23 19:13       ` Hannes Domani
2026-01-17 13:54   ` [PATCH v2 10/11] Move setting size of long " Hannes Domani
2026-01-21 15:59     ` Tom Tromey
2026-01-17 13:54   ` [PATCH v2 11/11] Add aarch64-windows support Hannes Domani
2026-01-17 16:04     ` Eli Zaretskii
2026-01-21 16:18     ` Tom Tromey
2026-01-23 19:14       ` Hannes Domani

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=1598131329.2278982.1768662915270@mail.yahoo.com \
    --to=ssbssa@yahoo.de \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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