From: Sverre Rabbelier <srabbelier@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Yesss! sourceforge.net and Git
Date: Sun, 1 Mar 2009 23:02:20 +0100 [thread overview]
Message-ID: <fabb9a1e0903011402y3d2878b1h7e29f720dbfe1c82@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903012259390.10279@pacific.mpi-cbg.de>
Heya,
On Sun, Mar 1, 2009 at 23:01, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> On Sun, 1 Mar 2009, Sverre Rabbelier wrote:
>> On Sun, Mar 1, 2009 at 22:38, Johannes Schindelin wrote:
>> > http://apps.sourceforge.net/trac/sitedocs/wiki/Git
It seems there's a bunch of sillyness in there, such as them
recommending backup over rsync?! They should be telling people to just
make a clone, and in the case of a crash they can push the clone back
up!
Also, maybe we can tell them git learned how to clone empty repo's recently?
>> About time! Totally awesome though.
>> Now, code.google.com and others have no excuse anymore, right? ;)
>
> Except that it is run by Subversion people, and therefore it by like
> asking git.or.cz to serve Mercurial repositories ;-)
Heh, speaking of Hg, I heard they're adding DVCS support to
code.google.com soon, if they're already adding a non-svn VCS, why not
git? :D
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-03-01 22:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 21:38 Yesss! sourceforge.net and Git Johannes Schindelin
2009-03-01 21:44 ` Sverre Rabbelier
2009-03-01 22:01 ` Johannes Schindelin
2009-03-01 22:02 ` Sverre Rabbelier [this message]
2009-03-01 22:07 ` Johannes Schindelin
2009-03-01 22:11 ` Sverre Rabbelier
2009-03-02 7:50 ` Miles Bader
2009-03-02 7:53 ` Sverre Rabbelier
2009-03-02 8:06 ` Felipe Contreras
2009-03-01 22:10 ` Felipe Contreras
2009-03-01 22:13 ` Sverre Rabbelier
2009-03-01 21:47 ` Grzegorz Kossakowski
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=fabb9a1e0903011402y3d2878b1h7e29f720dbfe1c82@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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.
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).