From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: koriakin@0x04.net (Marcin Kościelnicki)
Cc: gdb-patches@sourceware.org, palves@redhat.com
Subject: Re: [PATCH 1/8] gdb.trace: Fix write_inferior_data_ptr on 32-bit big-endian machines.
Date: Tue, 26 Jan 2016 13:50:00 -0000 [thread overview]
Message-ID: <20160126134950.CBA8A25D3@oc7340732750.ibm.com> (raw)
In-Reply-To: <56A7788B.6020900@0x04.net> from "=?UTF-8?Q?Marcin_Ko=c5=9bcielnicki?=" at Jan 26, 2016 02:45:47 PM
Marcin KoÃ
Âcielnicki wrote:
> I'll remove the duplicated function.
Thanks.
> Is there a chance of getting this patchset commited? I see I duplicated
> a good chunk of work done there, it's a matter of time before someone
> likewise stumbles upon other already-fixed issues...
Agreed. I've now pinged Wei-cheng off-list whether he's still planning
on committing this.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2016-01-26 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 13:57 Marcin Kościelnicki
2016-01-22 14:01 ` Pedro Alves
2016-01-22 14:06 ` Marcin Kościelnicki
2016-01-22 14:10 ` Pedro Alves
2016-01-26 13:32 ` Ulrich Weigand
2016-01-26 13:45 ` Marcin Kościelnicki
2016-01-26 13:50 ` Ulrich Weigand [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=20160126134950.CBA8A25D3@oc7340732750.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=koriakin@0x04.net \
--cc=palves@redhat.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