git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>, Elijah Newren <newren@gmail.com>
Subject: [PATCH] t5583: fix shebang line
Date: Fri, 12 May 2023 15:09:16 +0000	[thread overview]
Message-ID: <pull.1532.git.1683904156670.gitgitgadget@gmail.com> (raw)

From: Elijah Newren <newren@gmail.com>

The shebang was missing the leading `/` character, resulting in:

    $ ./t5583-push-branches.sh
    bash: ./t5583-push-branches.sh: cannot execute: required file not found

Add the missing character so the test can run.

Signed-off-by: Elijah Newren <newren@gmail.com>
---
    t5583: fix shebang line
    
    Applies on the top of tl/push-branches-is-an-alias-for-all.
    
    Noticed yesterday when testing my header cleanups against next & seen.

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1532%2Fnewren%2Ffix-tl-push-branches-is-an-alias-for-all-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1532/newren/fix-tl-push-branches-is-an-alias-for-all-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1532

 t/t5583-push-branches.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/t/t5583-push-branches.sh b/t/t5583-push-branches.sh
index 29a5c5601bd..e7e1b6dab66 100755
--- a/t/t5583-push-branches.sh
+++ b/t/t5583-push-branches.sh
@@ -1,4 +1,4 @@
-#!bin/sh
+#!/bin/sh
 
 test_description='check the consisitency of behavior of --all and --branches'
 

base-commit: 425b4d7f47bd2be561ced14eac36056390862e8c
-- 
gitgitgadget

                 reply	other threads:[~2023-05-12 15:09 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=pull.1532.git.1683904156670.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newren@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).