From: Martin Langhoff <martin.langhoff@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Wolfgang Denk <wd@denx.de>,
git@vger.kernel.org
Subject: Re: [OT?] git tools at SourceForge ?
Date: Sat, 13 Aug 2005 11:17:57 +1200 [thread overview]
Message-ID: <46a038f90508121617560d00c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0508121513530.3295@g5.osdl.org>
> - the git architecture is admirably suited to an _untrusted_ central
> server, ie exactly the SourceForge kind of setup. I realize that the
Definitely. And beyond that too. Using SF for CVS means that when SF's
CVS service is down (often enough) you can't commit (or even fscking
diff) until they are back up. Every single damn operation does a
roundtrip. This also means a huge load on their servers.
I'm sure SF will be glad to see CVS fall our of favour.
> Yes, developers can just merge with each other directly
I take it that you mean an exchange of patches that does not depend on
having public repos. What are the mechanisms available on that front,
other than patchbombs?
> This is _exactly_ where something like SF really ends up being helpful.
> It's a _hosting_ service, and git is eminently suitable to being
Not sure whether SF is offering rsync, but they do support hosting of
arbitrarty data -- and a project using GIT can use that to host
several developer trees . It'd be nice if SF offered gitweb and
similar niceties. As my usage of GIT increases, I may add support for
it on Eduforge.org
If I had more (hw/time) resources I'd do the git proxying of CVS
projects, but that's huge.
> And so I'd be thrilled to have some site like SF support it.
Eduforge's charter is to host education-related projects, so that's
not a free-for-all-comers, but I'm considering git support, as our
usage of git is growing.
cheers,
martin
next prev parent reply other threads:[~2005-08-12 23:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 19:07 [OT?] git tools at SourceForge ? Wolfgang Denk
2005-08-12 20:36 ` Junio C Hamano
2005-08-12 20:46 ` Daniel Barkalow
2005-08-12 21:06 ` Kirby C. Bohling
2005-08-12 22:01 ` Wolfgang Denk
2005-08-12 23:01 ` Martin Langhoff
2005-08-12 23:24 ` David Lang
2005-08-12 22:27 ` Linus Torvalds
2005-08-12 23:14 ` Daniel Barkalow
2005-08-12 23:17 ` Martin Langhoff [this message]
2005-08-12 23:46 ` Linus Torvalds
2005-08-13 1:16 ` Daniel Barkalow
-- strict thread matches above, loose matches on Subject: below --
2005-08-12 21:17 Marco Costalba
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=46a038f90508121617560d00c@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=wd@denx.de \
/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).