Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: tdaitx@linux.vnet.ibm.com (Tiago Stürmer Daitx)
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix complex argument handling in ppc64 dummy function call
Date: Tue, 02 Apr 2013 13:41:00 -0000	[thread overview]
Message-ID: <201304021245.r32CjgCu013483@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <1364789724.23407.59.camel@localhost.localdomain> from "Tiago =?ISO-8859-1?Q?St=FCrmer?= Daitx" at Apr 01, 2013 01:15:24 AM

Tiago Stürmer Daitxwrote:
> On Mon, 2013-03-11 at 17:11 +0100, Ulrich Weigand wrote:
> > With the minor formatting issues noted by Sergio and Pedro fixed,
> > this is OK.
> 
> Patch has been committed with the fixes. See
> http://sourceware.org/ml/gdb-cvs/2013-04/msg00002.html

Thanks!

> Err... I just noticed that it is appearing as April 1st in the cvs
> mailing list and I set the ChangeLog date as 2013-03-31. My mind was
> still on the wrong timezone. Please let me know if I need to fix that
> ChangeLog entry.

No worries.  As long as the ChangeLog entries are not out of order
with each other, this is fine.

> I suppose it's ok to ignore the wrong date in the commit log message (it
> says 2013-03-01, I forgot to update that), right?

Yes, this doesn't really matter.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


      reply	other threads:[~2013-04-02 12:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 18:30 Tiago Stürmer Daitx
2013-03-01  2:55 ` Sergio Durigan Junior
2013-03-01 17:50   ` Tiago Stürmer Daitx
2013-03-01 18:57     ` Sergio Durigan Junior
2013-03-01 20:07       ` Tiago Stürmer Daitx
2013-03-01 21:24     ` Pedro Alves
2013-03-01 23:42       ` Tiago Stürmer Daitx
2013-03-11 16:12     ` Ulrich Weigand
2013-04-01  4:15       ` Tiago Stürmer Daitx
2013-04-02 13:41         ` 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=201304021245.r32CjgCu013483@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdaitx@linux.vnet.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