From: David Bremner <david@tethera.net>
To: Austin Clements <amdragon@MIT.EDU>, notmuch@notmuchmail.org
Subject: Re: [PATCH] test: Remove #! line from test-lib.sh
Date: Thu, 29 Dec 2011 18:06:14 -0400 [thread overview]
Message-ID: <87obur6njd.fsf@zancas.localnet> (raw)
In-Reply-To: <1325126096-13885-1-git-send-email-amdragon@mit.edu>
On Wed, 28 Dec 2011 21:34:56 -0500, Austin Clements <amdragon@MIT.EDU> wrote:
> It makes no sense to run test-lib.sh, so it makes no sense to give it
> an interpreter. This is particularly annoying for Emacs users who
> have executable-insert set, since the presence of the #! line will
> cause Emacs to mark test-lib.sh executable when saving it, which will
> in turn case the 'basic' test to fail.
Pushed.
d
prev parent reply other threads:[~2011-12-29 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 2:34 [PATCH] test: Remove #! line from test-lib.sh Austin Clements
2011-12-29 4:56 ` Tomi Ollila
2011-12-29 22:06 ` David Bremner [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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87obur6njd.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=amdragon@MIT.EDU \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).