git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Public Gitweb Hosting Service
Date: Wed, 20 Sep 2006 02:48:28 +0200	[thread overview]
Message-ID: <20060920004828.GI8259@pasky.or.cz> (raw)

  Hi,

  there are various tiny repositories scatterred over the web that are
on crappy broken webhostings, don't have lifetime long enough and most
importantly have no gitweb interface for peeking inside - even e.g.
the StGIT repository suffers from that.

  To fix that problem, I've decided to quickly set up a public gitweb
hosting service. The deal is basically that you tell the system your
repository URL (designed only for reasonably small repositories; if you
have big repository, you ought to have the resources to host it) and it
will mirror the repository and provide gitweb interface for it, as well
as publish the mirror for cloning.

  It's running at

	http://repo.or.cz/

with latest Git and Gitweb from #next and few custom patches (I've
posted the interesting ones), all features enabled. If I get some
time, I will hopefully further improve the Gitweb interface (blame is
almost unusable, pickaxe is top secret functionality, etc.) and I will
generally try to track #next gitweb version closely (at least for the
start).

  This is still very experimental - I will watch how much interest, load
and traffic it generates; if it becomes unbearable, I will disable the
public mirror service and keep just the gitweb interface. Also, the web
interface is rather crude and you can currently use it only to register
new projects - if you want to make any adjustments to them, please drop
me a mail. Also please do if you have some cool ideas, or want to do a
nice design for the registration web interface. ;-)


  Note that there is also a glibc CVS import available at that address,
entirely coincidentally. That one is an exception and is not synced from
any other Git repository. It took git-cvsimport two days to chew through
on a decent machine (but over the network), the resulting size of 107M
is pretty nice. I hope to set it up to automatically track glibc CVS
further (and possibly other popular non-Git projects later).  There's
insane amount of tags which means the gitweb summary page takes "a bit"
long to load, I wonder if using packed refs would improve that.

  Have fun,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam

             reply	other threads:[~2006-09-20  0:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20  0:48 Petr Baudis [this message]
2006-09-20  1:01 ` [ANNOUNCE] Public Gitweb Hosting Service Jakub Narebski
2006-09-20  3:35 ` Linus Torvalds
2006-09-20 10:51   ` Petr Baudis
2006-09-20 15:05     ` Linus Torvalds
2006-09-21  0:45       ` Linus Torvalds
2006-09-21 22:42 ` Anand Kumria
2006-10-12 21:19 ` Nico -telmich- Schottelius

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=20060920004828.GI8259@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.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).