public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: "Rohr, Stephan via Gdb-patches" <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>,
	 "Rohr, Stephan" <stephan.rohr@intel.com>,
	Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH v3 1/1] gdb/dwarf2: Fix 'rw_pieced_value' for values casted to different type.
Date: Tue, 10 Jan 2023 14:31:02 -0700	[thread overview]
Message-ID: <87y1qa6prd.fsf@tromey.com> (raw)
In-Reply-To: <DM6PR11MB4564D7BCFAF84099D9BD5F9793FF9@DM6PR11MB4564.namprd11.prod.outlook.com> (Stephan via Gdb-patches Rohr's message of "Tue, 10 Jan 2023 09:29:14 +0000")

>> Thank you for your review.  This is my first patch.  Can you push it for me?
>> I don't have any write access.

Yep.  I fixed a whitespace error (an extra blank line at the end of the
test file) that git pointed out.

>> I plan to upstream more patches in the future and would like to have
>> "write after approval" access.  Could I put your email address in the field
>> which says "email address of person who approved request" in the application
>> form at https://sourceware.org/cgi-bin/pdw/ps_form.cgi ?

Yes.

Tom

      reply	other threads:[~2023-01-10 21:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 13:12 [PATCH v3 0/1] " Stephan Rohr
2022-12-21 13:12 ` [PATCH v3 1/1] " Stephan Rohr
2023-01-05 19:52   ` Tom Tromey
2023-01-06 19:22     ` Simon Marchi
2023-01-06 20:36       ` Tom Tromey
2023-01-09  8:12     ` Rohr, Stephan
2023-01-09 19:28       ` Tom Tromey
2023-01-10  9:29         ` Rohr, Stephan
2023-01-10 21:31           ` Tom Tromey [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=87y1qa6prd.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=stephan.rohr@intel.com \
    /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).