From: Joseph Myers <joseph@codesourcery.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: <gdb-patches@sourceware.org>, <binutils@sourceware.org>,
Simon Marchi <simon.marchi@ericsson.com>
Subject: Re: [PATCH 1/2] Bump to autoconf 2.69 and automake 1.15.1
Date: Mon, 18 Jun 2018 15:12:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1806181510050.23315@digraph.polyomino.org.uk> (raw)
In-Reply-To: <b121f2e5-77e7-b63d-a540-3db5d8203082@polymtl.ca>
On Fri, 15 Jun 2018, Simon Marchi wrote:
> - include: I'll need more precise guidance on how to sync
If a file in include/ is present in both trees (apart from ChangeLogs), it
should also have the same contents. However, each tree has some headers
of its own in include/ and there's no need to copy such headers from one
tree to the other.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-06-18 15:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 0:43 Simon Marchi
2018-06-15 0:46 ` [PATCH 2/2] Generated files Simon Marchi
2018-06-15 3:00 ` Simon Marchi
2018-06-15 14:22 ` [PATCH 1/2] Bump to autoconf 2.69 and automake 1.15.1 Nick Clifton
2018-06-15 14:38 ` Simon Marchi
2018-06-15 14:58 ` Nick Clifton
2018-06-15 15:14 ` Simon Marchi
2018-06-15 15:30 ` Nick Clifton
2018-06-15 15:38 ` Simon Marchi
2018-06-15 15:54 ` Nick Clifton
2018-06-16 1:39 ` Alan Modra
2018-06-16 3:56 ` Simon Marchi
2018-06-16 7:17 ` Andreas Schwab
2018-06-18 2:46 ` Alan Modra
2018-06-18 3:05 ` Simon Marchi
2018-06-18 9:42 ` Nick Clifton
2018-06-15 17:29 ` Joseph Myers
2018-06-16 3:05 ` Simon Marchi
2018-06-18 15:12 ` Joseph Myers [this message]
2018-06-18 15:32 ` Simon Marchi
2018-06-16 22:41 ` Andreas K. Huettel
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=alpine.DEB.2.20.1806181510050.23315@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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