From: Kris Shannon <kris.shannon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: [PATCH] Be consistent in naming of remote heads
Date: Wed, 17 Aug 2005 13:02:16 +1000 [thread overview]
Message-ID: <bf38a9f050816200274e28f31@mail.gmail.com> (raw)
The _remote_name variable used for messages does not need the
refs/heads/ prefix included.
Signed-off-by: Kris Shannon <kris.shannon@gmail.com>
---
git-parse-remote | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
9e7a4358b1792be188df87debf564e46acdb39d4
diff --git a/git-parse-remote b/git-parse-remote
--- a/git-parse-remote
+++ b/git-parse-remote
@@ -71,8 +71,8 @@ tag)
'')
_remote_head=HEAD ;;
*)
- _remote_head="refs/heads/$_remote_head"
_remote_name="head '$_remote_head' of $_remote_name"
+ _remote_head="refs/heads/$_remote_head"
;;
esac
;;
reply other threads:[~2005-08-17 3:03 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=bf38a9f050816200274e28f31@mail.gmail.com \
--to=kris.shannon@gmail.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.