From: Jakub Narebski <jnareb@gmail.com>
To: "Stephen Sinclair" <radarsat1@gmail.com>
Cc: "Neshama Parhoti" <pneshama@gmail.com>, git@vger.kernel.org
Subject: Re: Project Hosting with git ?
Date: Sat, 12 Jan 2008 09:46:01 -0800 (PST) [thread overview]
Message-ID: <m3fxx3lyz0.fsf@roke.D-201> (raw)
In-Reply-To: <9b3e2dc20801120845n15d59fe6q178ba257c12a28e0@mail.gmail.com>
"Stephen Sinclair" <radarsat1@gmail.com> writes:
> Neshama Parhoti wrote:
> > I mean, if I open a SourceForge project, I have to use cvs/subversion right ?
> >
> > Is there any way to use git ?
>
> There is currently an open feature request on sourceforge for git support.
> Please feel free to add a comment to the thread, hopefully if enough
> people do so they'll do something about it.
> (Though I wouldn't be surprised if they're working on it.)
>
> https://sourceforge.net/tracker/?func=detail&atid=350001&aid=1828327&group_id=1
Savannah, which is FOSS hosting site using SourceForge derived engine
(named Savane) has Git support. What is a bit strange is that its fork
Gna!, which also uses Savane, does not have Git support. This is because
Savannah runs "cleanup" branch of Savane while Gna! runs plain (?) Savane;
see http://git.or.cz/gitwiki/InterfacesFrontendsAndToolsWishlist#Savane
Alioth (Debian related projects hosting only) uses modified GForge
engine, which in turn is some fork of SourceForge engine, also has
git support.
Not that it helps much in adding Git support to SourceForge, as both
Savane and GForge are GPL, and IIRC SF.net engine is now closed-source.
> However, git works fine over http. I have a project on SF which I was
> using with subversion, but I recently switched the project over to
> git.
>
> I simply posted a bare git repo on the project website, and bang it's
> "hosted" on sourceforge. In order to automate things a bit, I set up
> a local repo which, when I push to it, runs git-update-server-info and
You need only to enable (chmod a+x) default update hook for that.
> then uses rsync to upload the repo changes to the SF web server.
>
> It seems to work fine. I do occasionally git-clone the http-hosted
> repo just to make sure things are still working, and so far no
> problems.
Nice solution, can be used in with any software hosting (BerliOS or
Sarovar for example) which provides rsync or other way of syncing.
> The downside is that SF will not collect statistics on the git repo.
> However, I've been using ohloh.net to track it instead, which works
> wonderfully.
You can use GitStat in the same way as you provide Git repository,
http://tree.celinuxforum.org/gitstat/
http://sourceforge.net/projects/gitstat/
http://www.ohloh.net/projects/8207?p=gitstat
but Ohloh have quite a nice features.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2008-01-12 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 13:53 Project Hosting with git ? Neshama Parhoti
2008-01-12 14:09 ` Grégoire Barbier
2008-01-12 15:27 ` Neshama Parhoti
2008-01-12 14:16 ` Pascal Obry
2008-01-12 15:28 ` Neshama Parhoti
2008-01-12 16:45 ` Stephen Sinclair
2008-01-12 17:41 ` Grégoire Barbier
2008-01-12 17:54 ` Stephen Sinclair
2008-01-12 18:01 ` Grégoire Barbier
2008-01-12 18:08 ` Stephen Sinclair
2008-01-12 17:46 ` Jakub Narebski [this message]
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=m3fxx3lyz0.fsf@roke.D-201 \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=pneshama@gmail.com \
--cc=radarsat1@gmail.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).