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

git init --initial-branch (should docs mention v2 protocol)

From
SSheik <sahibzone@gmail.com>
Date
Nov 5, 2023, 23:17 UTC
Message-ID
<9f17f398-83fa-4789-ace7-9230834519d3@gmail.com>
Hi Maintainers,

Currently it is not obvious from the docs that (git init --initial-branch) needs v2 protocol setup on ssh server for (git clone) to work properly with unborn refs, as seen in this email thread

 1. https://lore.kernel.org/git/63eb269e-72b9-4830-98fc-aeef8b8180d7@gmail.com/T/#u

Should a link to the v2 protocol documentation be added in "git init --initial-branch" to make this configuration more obvious for admins/users?

 1. https://git-scm.com/docs/git-init#Documentation/git-init.txt---initial-branchltbranch-namegt
 2. https://git-scm.com/docs/gitprotocol-v2

[System Info] git version: git version 2.42.0 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh uname: Linux 6.5.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.6-1 (2023-10-07) x86_64 compiler info: gnuc: 13.2 libc info: glibc: 2.37 $SHELL (typically, interactive shell): /bin/bash

[Enabled Hooks] not run from a git repository - no hooks to show

Thanks
Sheik
Message 1 of 1 in “git init --initial-branch (should docs mention v2 protocol)”
  1. SheikNov 5, 2023

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.