From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Stephon Harris <theonestep4@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Change permissions on git-completion.bash
Date: Wed, 04 Apr 2018 22:21:13 +0200 [thread overview]
Message-ID: <877epm205i.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <010201629243c44a-4a158009-aa68-4e05-ab54-f15a49ffb606-000000@eu-west-1.amazonses.com>
On Wed, Apr 04 2018, Stephon Harris wrote:
> Updating git-completion.bash to include instructions to change the
> permissions on the file when sourcing it in your .bashrc or .zshrc
> file.
But why is this needed? Files sourced by shells don't need to be
executable, and quoting the bash manual "The file searched for in PATH
need not be executable.".
What breaks for you / doesn't work because it doesn't have the +x bit?
prev parent reply other threads:[~2018-04-04 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 20:05 [PATCH] Change permissions on git-completion.bash Stephon Harris
2018-04-04 20:21 ` Ævar Arnfjörð Bjarmason [this message]
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=877epm205i.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=theonestep4@gmail.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;
as well as URLs for NNTP newsgroup(s).