From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, Ulrich.Weigand@de.ibm.com,
lgustavo@codesourcery.com (Luis Machado)
Subject: Re: [PATCH] S390: Fix undefined symbol "my_waitpid"
Date: Wed, 11 Sep 2013 11:42:00 -0000 [thread overview]
Message-ID: <87ioy737pt.fsf@br87z6lw.de.ibm.com> (raw)
In-Reply-To: <201309101507.r8AF7tHq012141@d06av02.portsmouth.uk.ibm.com> (Ulrich Weigand's message of "Tue, 10 Sep 2013 17:07:54 +0200 (CEST)")
"Ulrich Weigand" <uweigand@de.ibm.com> writes:
> At some point, it would probably be good to change this. (Maybe
> once we're off CVS and can actually do renames without losing
> history ...)
Right, that's probably a good idea. I'll keep that in mind after source
control has moved to GIT.
next prev parent reply other threads:[~2013-09-11 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 12:02 Andreas Arnez
2013-09-10 12:31 ` Joel Brobecker
2013-09-10 15:08 ` Ulrich Weigand
2013-09-11 11:42 ` Andreas Arnez [this message]
2013-09-18 18:39 ` Pedro Alves
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=87ioy737pt.fsf@br87z6lw.de.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=uweigand@de.ibm.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