From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/4] Add an include-checking script
Date: Fri, 19 Apr 2024 09:03:13 -0600 [thread overview]
Message-ID: <87plulxumm.fsf@tromey.com> (raw)
In-Reply-To: <87ttjxxv0u.fsf@tromey.com> (Tom Tromey's message of "Fri, 19 Apr 2024 08:54:41 -0600")
Tom> I wonder if this is some b4 thing since I modified the branch in a weird
Tom> way. I'll try again with b4 but if that fails again I will re-send the
Tom> normal way. And I guess stop using b4.
Yeah, b4 is sending from my backup branch for some reason.
I'll re-send using git send-email.
Tom
next prev parent reply other threads:[~2024-04-19 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 15:41 [PATCH v2 0/4] Add include guard checker and reformatter Tom Tromey
2024-04-18 15:41 ` [PATCH v2 1/4] Fix some minor header file irregularities Tom Tromey
2024-04-18 15:41 ` [PATCH v2 2/4] Add an include-checking script Tom Tromey
2024-04-18 19:25 ` Simon Marchi
2024-04-19 14:54 ` Tom Tromey
2024-04-19 15:03 ` Tom Tromey [this message]
2024-04-18 15:41 ` [PATCH v2 3/4] Add check-include-guards.py to pre-commit Tom Tromey
2024-04-18 15:41 ` [PATCH v2 4/4] Run check-include-guards.py Tom Tromey
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=87plulxumm.fsf@tromey.com \
--to=tromey@adacore.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).