git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Paul Williamson <paul.williamson@mediamiser.com>
To: Philip Oakley <philipoakley@iee.org>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: Switching branches not working in a cloned repo
Date: Mon, 19 Sep 2016 18:01:39 +0000	[thread overview]
Message-ID: <YQXPR01MB0023C5D73A5C4634D1D76E259EF40@YQXPR01MB0023.CANPRD01.PROD.OUTLOOK.COM> (raw)
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


  reply	other threads:[~2016-09-19 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 13:58 Switching branches not working in a cloned repo Paul Williamson
2016-09-19 16:16 ` Philip Oakley
2016-09-19 18:01   ` Paul Williamson [this message]
2016-09-19 19:50 ` Jacob Keller
2016-09-19 20:13   ` Paul Williamson

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YQXPR01MB0023C5D73A5C4634D1D76E259EF40@YQXPR01MB0023.CANPRD01.PROD.OUTLOOK.COM \
    --to=paul.williamson@mediamiser.com \
    --cc=git@vger.kernel.org \
    --cc=philipoakley@iee.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).