From: Alex Riesen <raa.lkml@gmail.com>
To: "Nathan W. Panike" <nathan.panike@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Tell users that git protocol is not for pushing
Date: Tue, 11 Nov 2008 08:24:55 +0100 [thread overview]
Message-ID: <20081111072455.GA4206@blimp.localdomain> (raw)
In-Reply-To: <1226379976-5959-1-git-send-email-nathan.panike@gmail.com>
Nathan W. Panike, Tue, Nov 11, 2008 06:06:16 +0100:
> When one attempts to push to a git-protocol repository, one gets the
> line:
>
> fatal: The remote end hung up unexpectedly
>
> This seems a bit obscure to me. It is better to inform the user that git://
> does not allow pushing.
But it does. See git daemon --help, look for receive-pack.
prev parent reply other threads:[~2008-11-11 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 5:06 [PATCH] Tell users that git protocol is not for pushing Nathan W. Panike
2008-11-11 7:24 ` Alex Riesen [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=20081111072455.GA4206@blimp.localdomain \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=nathan.panike@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).