From: Tom Tromey <tom@tromey.com>
To: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2][PR gdb/24789] Allow pointer arithmetic with integer references
Date: Wed, 01 Apr 2020 12:06:56 -0600 [thread overview]
Message-ID: <87wo6z2i7z.fsf@tromey.com> (raw)
In-Reply-To: <576703007.1029840.1585762590985@mail.yahoo.com> (Hannes Domani via Gdb-patches's message of "Wed, 1 Apr 2020 17:36:30 +0000 (UTC)")
>>>>> "Hannes" == Hannes Domani via Gdb-patches <gdb-patches@sourceware.org> writes:
Hannes> That leads me to another question, who/when are PRs closed after
Hannes> pushing?
Someone has to do it manually. If I fix a bug, normally I do it myself
after pushing.
If you do this, be sure to set the target milestone on the bug.
That makes it easy to search for bugs closed in a given release.
If I don't know the release, I tend to leave it blank, though it's also
ok if you want to dig through the git log to find the answer.
I'll look at the ones you mentioned.
Tom
next prev parent reply other threads:[~2020-04-01 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200331220655.4436-1-ssbssa.ref@yahoo.de>
2020-03-31 22:06 ` Hannes Domani
2020-04-01 16:36 ` Tom Tromey
2020-04-01 17:17 ` Hannes Domani
2020-04-01 17:36 ` Hannes Domani
2020-04-01 18:06 ` Tom Tromey [this message]
[not found] ` <87sghn2i0g.fsf@tromey.com>
2020-04-01 18:14 ` Hannes Domani
2020-04-01 18:55 ` 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=87wo6z2i7z.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@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