From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Bruce Korb <bruce.korb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Next problem... (thank you in advance :)
Date: Sun, 20 Sep 2009 21:03:47 +0200 [thread overview]
Message-ID: <vpqtyyxtp4c.fsf@bauges.imag.fr> (raw)
In-Reply-To: <4AB67A22.4010004@gmail.com> (Bruce Korb's message of "Sun\, 20 Sep 2009 11\:53\:22 -0700")
Bruce Korb <bruce.korb@gmail.com> writes:
> $ git push
> fatal: The remote end hung up unexpectedly
>
> Trying to push to Source Forge:
http://www.google.com/search?q=sourceforge+git+push
For me, the answer is in the first link, near "read-only", and even
closer to "read/write" ;-).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
prev parent reply other threads:[~2009-09-20 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 18:53 Next problem... (thank you in advance :) Bruce Korb
2009-09-20 19:03 ` Matthieu Moy [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=vpqtyyxtp4c.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=bruce.korb@gmail.com \
--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).