From: Luca Barbato <lu_zero@gentoo.org>
To: Donnie Berkholz <dberkholz@gentoo.org>
Cc: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] DVCS update
Date: Wed, 11 Feb 2009 14:30:09 +0100 [thread overview]
Message-ID: <4992D2E1.6040403@gentoo.org> (raw)
In-Reply-To: <20090210215134.GE3692@comet>
Donnie Berkholz wrote:
> - Robin has commented that he doesn't know what kind of server-side
> resources are required. I've talked to a number of git admins
> (kernel.org, fedora, freedesktop.org, gnome), and they have all said the
> hardware requirements for git are negligible. They don't have any
> resource on their servers that's being used up. It's gitweb that is
> somewhat resource-intensive.
cgit could be a valid alternative.
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
next prev parent reply other threads:[~2009-02-11 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 21:51 [gentoo-council] DVCS update Donnie Berkholz
2009-02-10 22:08 ` Robin H. Johnson
2009-02-10 23:06 ` Donnie Berkholz
2009-02-11 13:30 ` Luca Barbato [this message]
2009-02-11 19:19 ` Donnie Berkholz
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=4992D2E1.6040403@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=dberkholz@gentoo.org \
--cc=gentoo-council@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox