public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31645] Mismatched include guards in gdb/arch/csky.h
Date: Wed, 17 Apr 2024 13:40:07 +0000 [thread overview]
Message-ID: <bug-31645-4717-MTr2vu5AUx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31645-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31645
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |15.1
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Matt Wozniski from comment #2)
> If you won't accept patches on bugzilla, it should probably not suggest "Add
> an attachment (proposed patch, testcase, etc.)" when filing a bug rpeort.
>
> I've emailed the patch to the mailing list, though setting up `git
> send-email` to work with gmail took me around 20 minutes to figure out,
> which seems pretty excessive for a 1 character diff. Refusing to look at
> patches on the bug tracker seems pretty hostile to drive-by contributions.
Yeah, but it's also a cultural thing that's hard to change.
Thank you for the patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-04-17 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 23:28 [Bug gdb/31645] New: " godlygeek at gmail dot com
2024-04-16 13:31 ` [Bug gdb/31645] " tromey at sourceware dot org
2024-04-16 21:26 ` godlygeek at gmail dot com
2024-04-17 13:39 ` cvs-commit at gcc dot gnu.org
2024-04-17 13:40 ` tromey at sourceware dot org [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=bug-31645-4717-MTr2vu5AUx@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).