From: John Baldwin <jhb@FreeBSD.org>
To: Simon Marchi <simon.marchi@ericsson.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [PATCH] Carry the gnulib getcwd backport as a patch
Date: Tue, 18 Sep 2018 21:33:00 -0000 [thread overview]
Message-ID: <ad91b799-c0c4-47fe-fb72-68438a561e3d@FreeBSD.org> (raw)
In-Reply-To: <20180918212124.5851-1-simon.marchi@ericsson.com>
On 9/18/18 2:21 PM, Simon Marchi wrote:
> Commit
>
> e2fc52e7457 ("Fix PR gdb/23558: Use system's 'getcwd' when cross-compiling GDB")
>
> backported some changes from a future gnulib version to our import.
> However, this means that every time someone wants to change our gnulib
> import (e.g. add a module), they must make sure not to include that
> backported change. It also means that someone running the
> update-gnulib.sh script without changes will get some diffs and wonder
> why.
>
> Instead, I suggest we carry that backport as a patch applied by the
> update-gnulib.sh script after running the import tool. It will make it
> clear what backport or local modification we have and should make
> running update-gnulib.sh give a reproducible result.
>
> There is a hunk in the configure file in this patch, this is because the
> commit that backported the getcwd bits didn't include the re-generated
> configure.
This looks good to me. I've verified it generates ok for me on a FreeBSD host
as well.
--
John Baldwin
                                                                           Â
next prev parent reply other threads:[~2018-09-18 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 21:21 Simon Marchi
2018-09-18 21:33 ` John Baldwin [this message]
2018-09-18 21:39 ` Tom Tromey
2018-09-18 21:49 ` Simon Marchi
[not found] ` <87woriqxmj.fsf@tromey.com>
2018-09-18 21:59 ` Simon Marchi
2018-09-19 2:42 ` Sergio Durigan Junior
2018-09-19 3:49 ` Simon Marchi
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=ad91b799-c0c4-47fe-fb72-68438a561e3d@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=simon.marchi@ericsson.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