From: "Grégoire Barbier" <devel@gbarbier.org>
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 18:41:50 +0100 [thread overview]
Message-ID: <4788FBDE.6090903@gbarbier.org> (raw)
In-Reply-To: <9b3e2dc20801120845n15d59fe6q178ba257c12a28e0@mail.gmail.com>
Stephen Sinclair a écrit :
> 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 disagree: git does not work "fine" over http, it only works fine for
fetch/pull.
At less with last versions, push over http/webdav does not work (and by
the way corrupts the remote repository, by changing the HEAD sha without
uploading related objects).
I initiated a thread about that on the list a few weeks ago, with
subject "git over webdav: what can I do for improving http-push ?".
However I did not (yet?) post a patch.
> 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
> then uses rsync to upload the repo changes to the SF web server.
I agree with this: if you push locally and then upload, it works fine.
With rsync, ftp, sftp or whatever you want.
--
Grégoire Barbier - gb à gbarbier.org - +33 6 21 35 73 49
next prev parent reply other threads:[~2008-01-12 17:42 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 [this message]
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
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=4788FBDE.6090903@gbarbier.org \
--to=devel@gbarbier.org \
--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).