public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 760dcf: Unbreak 4.9.3.
Date: Mon, 14 Nov 2016 19:24:00 -0000	[thread overview]
Message-ID: <582a0f53b8377_70c3fcfc45af1307156a@hookshot-fe6-cp1-prd.iad.github.net.mail> (raw)

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

  Branch: refs/heads/master
  Home:   https://github.com/crosstool-ng/crosstool-ng
  Commit: 760dcf2b39c89acb48db6590ff4f0b73df0f4f2f
      https://github.com/crosstool-ng/crosstool-ng/commit/760dcf2b39c89acb48db6590ff4f0b73df0f4f2f
  Author: Alexey Neyman <stilor@att.net>
  Date:   2016-11-11 (Fri, 11 Nov 2016)

  Changed paths:
    M patches/gcc/4.9.3/120-gcc-config.gcc-fix-typo-for-powerpc-e6500-cpu_is_64b.patch

  Log Message:
  -----------
  Unbreak 4.9.3.

The patch provided by the original submitter did not apply cleanly to 4.9.3; had a fuzz 2.
We only allow fuzz 1. Fix up the patch.

Signed-off-by: Alexey Neyman <stilor@att.net>


  Commit: 51b7d69bbc7e4c61d6eb7c664d8ffeab66c23298
      https://github.com/crosstool-ng/crosstool-ng/commit/51b7d69bbc7e4c61d6eb7c664d8ffeab66c23298
  Author: Alexey Neyman <stilor@att.net>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M patches/gcc/4.9.3/120-gcc-config.gcc-fix-typo-for-powerpc-e6500-cpu_is_64b.patch

  Log Message:
  -----------
  Merge pull request #474 from stilor/unbreak-gcc-4.9.3

Unbreak 4.9.3.


Compare: https://github.com/crosstool-ng/crosstool-ng/compare/8fbe000639d4...51b7d69bbc7e

[-- Attachment #2: Type: text/plain, Size: 71 bytes --]

--
For unsubscribe information see http://sourceware.org/lists.html#faq

                 reply	other threads:[~2016-11-14 19:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=582a0f53b8377_70c3fcfc45af1307156a@hookshot-fe6-cp1-prd.iad.github.net.mail \
    --to=stilor@att.net \
    --cc=crossgcc@sourceware.org \
    /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).