From: Tom Tromey <tromey@redhat.com>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Have regdat.sh always rewrite the output register file
Date: Mon, 13 Jan 2014 19:52:00 -0000 [thread overview]
Message-ID: <87wqi31wxn.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1389326150-14874-1-git-send-email-patrick@parcs.ath.cx> (Patrick Palka's message of "Thu, 9 Jan 2014 22:55:50 -0500")
>>>>> "Patrick" == Patrick Palka <patrick@parcs.ath.cx> writes:
Patrick> +2014-01-10 Patrick Palka <patrick@parcs.ath.cx>
Patrick> +
Patrick> + * regformats/regdat.sh: Always rewrite the register file.
Patrick> +
This is ok. I'll push it momentarily.
Do you have a copyright assignment in place?
I think this particular patch falls under the limit, following the "one
way to write it" rule; but if you don't have an assignment, it would be
good to get one for future patches. Contact me off-list if you need this.
Tom
prev parent reply other threads:[~2014-01-13 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 3:56 Patrick Palka
2014-01-13 19:52 ` 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=87wqi31wxn.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=patrick@parcs.ath.cx \
/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).