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

how to clone/checkout branch/tag vesion from GIT repository

From
Ssupadhyay <supadhyay@imany.com>
Date
May 10, 2012, 13:39 UTC
Message-ID
<1336657187852-7546744.post@n2.nabble.com>
Hi All,

I try to use below command to do clone from particular branch/version number. I used below command...

$ git clone -b br6-1-0 ssh://gitolite@myservername/testrep Cloning into 'testrep'... remote: Counting objects: 19536, done. remote: Compressing objects: 100% (5850/5850), done. remote: Total 19536 (delta 13869), reused 18869 (delta 13202) Receiving objects: 100% (19536/19536), 61.44 MiB | 17 KiB/s, done. Resolving deltas: 100% (13869/13869), done. warning: Remote branch br6-0 not found in upstream origin, using HEAD instead

End user query is - they want the clone from particular branch which is separate from Head so I run above commmand. Can any one please help me how to resolve this?

Is there any way to findout how many branches are available in my GIT repository. 

Thanks in advance...

-- View this message in context: http://git.661346.n2.nabble.com/how-to-clone-checkout-branch-tag-vesion-from-GIT-repository-tp7546744.html Sent from the git mailing list archive at Nabble.com.

Next: Jeff King
Message 1 of 9 in “how to clone/checkout branch/tag vesion from GIT repository”
  1. supadhyayMay 10, 2012
  2. Jeff KingMay 10, 2012
  3. Suchi UpadhyayMay 10, 2012
  4. Jeff KingMay 10, 2012
  5. supadhyayMay 11, 2012
  6. Jeff KingMay 11, 2012
  7. supadhyayMay 12, 2012
  8. supadhyayMay 14, 2012
  9. Jeff KingMay 14, 2012

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.