From: Simon Marchi <simark@simark.ca>
To: bug-hurd@gnu.org, gdb-patches@sourceware.org, thomas@codesourcery.com
Subject: Re: hurd: PIE support
Date: Thu, 28 Dec 2017 02:05:00 -0000 [thread overview]
Message-ID: <9427bbb8-edc2-d493-c4df-61f15d637f55@simark.ca> (raw)
In-Reply-To: <20171227154435.rjlz4w73t7lbsucy@var.youpi.perso.aquilenet.fr>
On 2017-12-27 10:44 AM, Samuel Thibault wrote:
> Hello,
>
> Simon Marchi, on mar. 26 déc. 2017 21:48:23 -0500, wrote:
>> We would also need a ChangeLog entry.
>
> Well, I had put a ChangeLog entry at the top of the posted file. Is
> something else needed? In the patch I have just sent to the list I have
> directly put the gdb/ChangeLog update in addition to the commit message
> log. If that is what is wanted, then the gdb/CONTRIBUTE file should be
> update, otherwise frustration happens on both sides.
>
> Samuel
>
Ah, sorry I missed it. I ended up using git-apply to apply the patch (git-am
wouldn't work), which looses the information before the diff.
I'll reply to the other mail.
Simon
prev parent reply other threads:[~2017-12-28 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 17:13 Samuel Thibault
2017-12-27 2:48 ` Simon Marchi
2017-12-27 15:44 ` Samuel Thibault
2017-12-28 2:05 ` Simon Marchi [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=9427bbb8-edc2-d493-c4df-61f15d637f55@simark.ca \
--to=simark@simark.ca \
--cc=bug-hurd@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=thomas@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).