git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kristian Høgsberg" <krh@bitplanet.net>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Johan Herland" <johan@herland.net>,
	git@vger.kernel.org, "Lars Hjemli" <hjemli@gmail.com>,
	"Jakub Narebski" <jnareb@gmail.com>
Subject: Re: CGit and repository list
Date: Sun, 14 Sep 2008 13:22:12 -0400	[thread overview]
Message-ID: <59ad55d30809141022r6973155fh933976d25ef4cf01@mail.gmail.com> (raw)
In-Reply-To: <59ad55d30809141014x2160d50dqb8ac20b4c108b4e1@mail.gmail.com>

On Sun, Sep 14, 2008 at 1:14 PM, Kristian Høgsberg <krh@bitplanet.net> wrote:
> The script we're using on freedesktop.org is something like this:
>
>  http://people.freedesktop.org/~krh/find-repos.sh
>
> which isn't too scary.  We run it from a cron script, every ten
> minutes or so.  It's much better than  rescanning all the dirs every
> time somebody requests the repo listing (we have a lot of repos, check
> cgit.freedesktop.org).  We have no need for cgit to to this
> automatically on every request, and I don't see us using that feature
> if it gets implemented.

A feature that would be useful, though, would be support for listing a
sub-set of repos... for example, cgit.freedesktop.org/~krh would list
just my repos and cgit.freedesktop.org/xorg/driver would list all the
X.org driver repos.  Another idea is a javascript/css frontpage that
supports folding repos away according to the groups and possibly
common path elements in the url.  For example:

  [+] Freedesktop Repositories
  [-] User repositories
      [+] ~agdf5
      [+] ~ahuillet
      ...
      [-] ~krh
           ~krh/akamaru
           ~krh/bugzilla
           ~krh/compiz
      [-] ~kyle

etc.

Just throwing out a couple of ideas.

cheers,
Kristian

  reply	other threads:[~2008-09-14 17:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12  4:47 configuring git public repository sagi4
2008-09-12 12:33 ` Ciprian Dorin Craciun
2008-09-12 12:57   ` Jakub Narebski
2008-09-12 14:36     ` Lars Hjemli
2008-09-12 14:58       ` CGit and repository list Petr Baudis
2008-09-12 15:10         ` Lars Hjemli
     [not found]           ` <200809121812.40920.johan@herland.net>
2008-09-12 22:48             ` Petr Baudis
2008-09-12 23:20               ` Lars Hjemli
2008-09-13 19:49                 ` Petr Baudis
2008-09-13 20:02                   ` Lars Hjemli
2008-09-14  7:53                     ` [CGIT PATCH] parsing.c: handle unexpected commit/tag content Lars Hjemli
2008-09-14  8:52                       ` Lars Hjemli
2008-09-15 22:04                   ` CGit and repository list Lars Hjemli
2008-09-14 17:14               ` Kristian Høgsberg
2008-09-14 17:22                 ` Kristian Høgsberg [this message]
2008-09-14 18:01                   ` Lars Hjemli
2008-09-12 15:54         ` Jakub Narebski
2008-09-12 16:00           ` Shawn O. Pearce
2008-09-12 16:12             ` Lars Hjemli
2008-09-12 16:05           ` Petr Baudis
2008-09-12 16:08             ` Shawn O. Pearce
2008-09-12 16:20               ` Petr Baudis
2008-09-12 16:22                 ` Shawn O. Pearce
2008-09-12 17:40             ` Jakub Narebski
2008-09-12 17:45               ` Shawn O. Pearce
2008-09-12 19:13               ` Petr Baudis

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=59ad55d30809141022r6973155fh933976d25ef4cf01@mail.gmail.com \
    --to=krh@bitplanet.net \
    --cc=git@vger.kernel.org \
    --cc=hjemli@gmail.com \
    --cc=jnareb@gmail.com \
    --cc=johan@herland.net \
    --cc=pasky@suse.cz \
    /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).