git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH/RFC] git-request-pull: replace call to deprecated peek-remote

From
Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Date
Jul 8, 2008, 23:32 UTC
Message-ID
<4873F8FF.70607@ramsay1.demon.co.uk>
Signed-off-by: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
---
I don't even recall how I noticed this ...

Only very lightly tested, but since git-peek-remote and git-ls-remote are implemented in git.c as synonyms, it should be quite safe ...

 git-request-pull.sh |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-request-pull.sh b/git-request-pull.sh
index 068f5e0..073a314 100755
--- a/git-request-pull.sh
+++ b/git-request-pull.sh
@@ -26,7 +26,7 @@ merge_base=`git merge-base $baserev $headrev` ||
 die "fatal: No commits in common between $base and $head"
 
 url=$(get_remote_url "$url")
-branch=$(git peek-remote "$url" \
+branch=$(git ls-remote "$url" \
 	| sed -n -e "/^$headrev	refs.heads./{
 		s/^.*	refs.heads.//
 		p
-- 
1.5.6
Message 1 of 1 in “git-request-pull: replace call to deprecated peek-remote”
  1. git-request-pull: replace call to deprecated peek-remoteRamsay Jones, Jul 8, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.