On 05/13/2016 01:55 AM, Jakub Sejdak wrote:
+2016-05-13 Jakub Sejdak
+* config.guess: Import version 2016-04-02 (newest).
+* config.sub: Import version 2016-05-10 (newest).
Installed on the trunk. I think this was NAK's for the release branches.
jeff
Ping.
2016-05-14 13:36 GMT+02:00 Jakub Sejdak :
> So please confirm that this is OK for trunk only and apply it.
> Then I will start working on backporting this for other branches.
>
> 2016-05-14 11:29 GMT+02:00 Mike Stump :
>> On May 14, 2016, at 1:15 AM, Jakub Sejdak wrote:
>>> Then when those
So please confirm that this is OK for trunk only and apply it.
Then I will start working on backporting this for other branches.
2016-05-14 11:29 GMT+02:00 Mike Stump :
> On May 14, 2016, at 1:15 AM, Jakub Sejdak wrote:
>> Then when those scripts get copied 'as they are' from GNU config? Only
>>
On May 14, 2016, at 1:15 AM, Jakub Sejdak wrote:
> Then when those scripts get copied 'as they are' from GNU config? Only
> for newly created branches?
Only for trunk...
OK so just one final question to be clear: This patch was created from
trunk with config,sub and config.guess copied from GNU config
upstream.
If you say, that I should just modify bits for my port, then this
patch is still bad (since it modifies much more).
Then when those scripts get copied 'as
On May 13, 2016, at 11:50 AM, Jakub Sejdak wrote:
>
> OK I understand. So am I right, that in such a case there is no way to
> introduce new OS targets to branch 4.9 and 5?
No. You just hand edit in the bits you need for your port, and seek approval
for that.
In general, all new work goes int
OK I understand. So am I right, that in such a case there is no way to
introduce new OS targets to branch 4.9 and 5?
What about 6 branch and trunk?
On the other hand: this is my first patch and I'm not quite familiar
with the procedure of applying patches to upstream. Who should upload
my patch, w
On Fri, 13 May 2016, Jakub Sejdak wrote:
> Is it OK for trunk, gcc-4.9, gcc-5 and gcc-6 branches?
It's not appropriate to update these scripts from upstream on release
branches. For example, config.guess changed a while back to output
x86_64-pc-linux-gnu in place of x86_64-unknown-linux-gnu, a
Is it OK for trunk, gcc-4.9, gcc-5 and gcc-6 branches?
2016-05-13 9:52 GMT+02:00 Jakub Sejdak :
> From: Kuba Sejdak
>
> ---
> ChangeLog| 4 +++
> config.guess | 93
>
> config.sub | 8 --
> 3 files changed, 59 insertions(+
From: Kuba Sejdak
---
ChangeLog| 4 +++
config.guess | 93
config.sub | 8 --
3 files changed, 59 insertions(+), 46 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index eac1cc6..e092878 100644
--- a/ChangeLog
+++ b/Change
10 matches
Mail list logo
