public inbox for newlib-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org> To: newlib-cvs@sourceware.org Subject: [newlib-cygwin] remove +x bit on source files Date: Thu, 22 Dec 2022 03:40:25 +0000 (GMT) [thread overview] Message-ID: <20221222034025.A905E3858281@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=0a7bf8fc4c061d550bae6668a6e2cd03c67dce46 commit 0a7bf8fc4c061d550bae6668a6e2cd03c67dce46 Author: Mike Frysinger <vapier@gentoo.org> Date: Wed Dec 21 22:38:57 2022 -0500 remove +x bit on source files These should never be marked executable as they have no shebang and are pure source files. Diff: --- include/elf/epiphany.h | 0 include/opcode/bfin.h | 0 newlib/libc/machine/w65/lshrhi.S | 0 newlib/libc/machine/w65/sdivhi3.S | 0 newlib/libc/machine/w65/smulhi3.S | 0 newlib/libc/machine/w65/udivhi3.S | 0 newlib/libc/machine/w65/umodhi3.S | 0 newlib/libc/sys/rdos/chown.c | 0 newlib/libc/sys/rdos/fork.c | 0 newlib/libc/sys/rdos/fstat.c | 0 newlib/libc/sys/rdos/lseek.c | 0 newlib/libc/sys/rdos/open.c | 0 newlib/libc/sys/rdos/rdos.h | 0 newlib/libc/sys/rdos/readlink.c | 0 newlib/libc/sys/rdos/stat.c | 0 newlib/libc/sys/rdos/symlink.c | 0 16 files changed, 0 insertions(+), 0 deletions(-) diff --git a/include/elf/epiphany.h b/include/elf/epiphany.h old mode 100755 new mode 100644 diff --git a/include/opcode/bfin.h b/include/opcode/bfin.h old mode 100755 new mode 100644 diff --git a/newlib/libc/machine/w65/lshrhi.S b/newlib/libc/machine/w65/lshrhi.S old mode 100755 new mode 100644 diff --git a/newlib/libc/machine/w65/sdivhi3.S b/newlib/libc/machine/w65/sdivhi3.S old mode 100755 new mode 100644 diff --git a/newlib/libc/machine/w65/smulhi3.S b/newlib/libc/machine/w65/smulhi3.S old mode 100755 new mode 100644 diff --git a/newlib/libc/machine/w65/udivhi3.S b/newlib/libc/machine/w65/udivhi3.S old mode 100755 new mode 100644 diff --git a/newlib/libc/machine/w65/umodhi3.S b/newlib/libc/machine/w65/umodhi3.S old mode 100755 new mode 100644 diff --git a/newlib/libc/sys/rdos/chown.c b/newlib/libc/sys/rdos/chown.c old mode 100755 new mode 100644 diff --git a/newlib/libc/sys/rdos/fork.c b/newlib/libc/sys/rdos/fork.c old mode 100755 new mode 100644 diff --git a/newlib/libc/sys/rdos/fstat.c b/newlib/libc/sys/rdos/fstat.c old mode 100755 new mode 100644 diff --git a/newlib/libc/sys/rdos/lseek.c b/newlib/libc/sys/rdos/lseek.c old mode 100755 new mode 100644 diff --git a/newlib/libc/sys/rdos/open.c b/newlib/libc/sys/rdos/open.c old mode 100755 new mode 100644 diff --git a/newlib/libc/sys/rdos/rdos.h b/newlib/libc/sys/rdos/rdos.h old mode 100755 new mode 100644 diff --git a/newlib/libc/sys/rdos/readlink.c b/newlib/libc/sys/rdos/readlink.c old mode 100755 new mode 100644 diff --git a/newlib/libc/sys/rdos/stat.c b/newlib/libc/sys/rdos/stat.c old mode 100755 new mode 100644 diff --git a/newlib/libc/sys/rdos/symlink.c b/newlib/libc/sys/rdos/symlink.c old mode 100755 new mode 100644
reply other threads:[~2022-12-22 3:40 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=20221222034025.A905E3858281@sourceware.org \ --to=vapier@sourceware.org \ --cc=newlib-cvs@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: linkBe 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).