From: Pedro Alves <palves@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Fix "info frame" in the outermost frame.
Date: Fri, 06 Dec 2013 20:01:00 -0000 [thread overview]
Message-ID: <52A22D0D.7060002@redhat.com> (raw)
In-Reply-To: <1385756149-534-1-git-send-email-palves@redhat.com>
FYI, I've pushed this.
Andrew, I had been playing with git commit --amend --date,
and reset the author of patch 1 to me by mistake. I only
noticed it too late, after pushing... sorry.
--
Pedro Alves
prev parent reply other threads:[~2013-12-06 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 20:16 Pedro Alves
2013-11-29 20:20 ` [PATCH 2/2] " Pedro Alves
2013-12-02 9:04 ` Yao Qi
2013-12-02 10:05 ` Pedro Alves
[not found] ` <52A3DBA6.6060706@codesourcery.com>
2013-12-09 10:58 ` Pedro Alves
2013-11-29 20:39 ` [PATCH 1/2] New OPTIMIZED_OUT_ERROR error code Pedro Alves
2013-12-02 13:53 ` Andrew Burgess
2013-12-06 20:01 ` Pedro Alves [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=52A22D0D.7060002@redhat.com \
--to=palves@redhat.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