List for cgit developers and users
 help / color / mirror / Atom feed
From: terrence.j.dunnigan at boeing.com (Dunnigan, Terrence J)
Subject: Missing branches
Date: Wed, 23 Sep 2015 01:26:14 +0000	[thread overview]
Message-ID: <9AD8B655B5126D4FAE1397203CDDBF2D21B850@XCH-PHX-205.sw.nos.boeing.com> (raw)
In-Reply-To: <20150922224222.GL17201@serenity.lan>

The missing branches neither appear on the summary page nor the refs page, even after cleaning the browser cache.

When I run 'git for-each-ref' in the git repository on the git server I see all of the branches. 

It's as if cgit is looking at an older version of the repo, even though the scan path points to the same directory in which I just performed 'git for-each-ref'.

Terry

 

-----Original Message-----
From: John Keeping [mailto:john at keeping.me.uk] 
Sent: Tuesday, September 22, 2015 5:42 PM
To: Dunnigan, Terrence J
Cc: cgit at lists.zx2c4.com
Subject: Re: Missing branches

On Tue, Sep 22, 2015 at 09:25:19PM +0000, Dunnigan, Terrence J wrote:
> One of our cgit instances (0.10.1) is not displaying all branches in a 
> repo. We've turned caching off (cache-size = 0) and deleted the cache 
> under /var/cache/cgit, and we are still missing branches.
> 
> The branches are missing from multiple repos. We've verified that 
> scan-path points to the correct directory, and that the git repository 
> directory actually has the missing branches.
> 
> For some reason, cgit is just not displaying all of the branches. One 
> repo has 5 branches yet cgit only displays 2, for example.

Do you mean on the summary page or the refs page?  The refs page should show everything but the summary page will only show the number allowed by the "summary-tags" and "summary-branches" configuration variables, although those default to 10.

Can you run `git for-each-ref` in the repository CGit is displaying to see if the branches show up there?  CGit should be displaying everything under "refs/heads/".


  reply	other threads:[~2015-09-23  1:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 21:25 terrence.j.dunnigan
2015-09-22 22:42 ` john
2015-09-23  1:26   ` terrence.j.dunnigan [this message]
2015-09-23  8:52     ` john
2015-09-24 21:52       ` terrence.j.dunnigan

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

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

  git send-email \
    --in-reply-to=9AD8B655B5126D4FAE1397203CDDBF2D21B850@XCH-PHX-205.sw.nos.boeing.com \
    --to=cgit@lists.zx2c4.com \
    /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.
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 NNTP newsgroup(s).