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

RE: Switching branches not working in a cloned repo

From
Paul Williamson <paul.williamson@mediamiser.com>
Date
Sep 19, 2016, 18:01 UTC
Message-ID
<YQXPR01MB0023C5D73A5C4634D1D76E259EF40@YQXPR01MB0023.CANPRD01.PROD.OUTLOOK.COM>
In-Reply-To
<3999677D12354A3CB2035E932353981A@PhilipOakley>
-----Original Message-----
From: Philip Oakley [mailto:philipoakley@iee.org] 
>Have you tried `git ls-remote` ?
>The `branch -r` just lists the local 'rtb's (IIUC).
Nice, I didn't know about that command - I tried it though and it does list the remote branches correctly. I checked the commit refs given and it tallies with the refs at the gitolite server end.
>It could be someone has accidently pruned or deleted that branch at the remote.
I don't think so, as I say it's a gitolite server, so usually nobody is on it. We just push to it and set up post-receive hooks for if updates need to be pushed on to a deployment server.
Do you know of ways to check if anything is corrupted within the repo? I ran git fsck, but that didn't show up anything.
>What version are you (they) on?
1.9.1 at both ends (my laptop and our gitolite server)
> Gmane had to quit. Try http://public-inbox.org/git (see the help link)
Ah! Thanks. I tried searching but so far only turned up this thread.
> philip 
Thanks for your reply, Philip.
Paul
Previous: Philip OakleyNext: Jacob Keller
Message 3 of 5 in “Switching branches not working in a cloned repo”
  1. Paul WilliamsonSep 19, 2016
  2. Philip OakleySep 19, 2016
  3. Paul WilliamsonSep 19, 2016
  4. Jacob KellerSep 19, 2016
  5. Paul WilliamsonSep 19, 2016

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.