From: Andreas Ericsson <ae@op5.se>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, Nicolas Pitre <nico@cam.org>,
"Shawn O. Pearce" <spearce@spearce.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Efficiency of initial clone from server
Date: Tue, 13 Feb 2007 16:03:08 +0100 [thread overview]
Message-ID: <45D1D32C.1070900@op5.se> (raw)
In-Reply-To: <9e4733910702112053q2c196ddcr970a062281d332b7@mail.gmail.com>
Jon Smirl wrote:
> On 2/11/07, Junio C Hamano <junkio@cox.net> wrote:
>> "Jon Smirl" <jonsmirl@gmail.com> writes:
>>
>> > jonsmirl@jonsmirl:/extra$ git clone
>> > git://git.kernel.org/pub/scm/linux/kernel/gt/linville/wireless-dev.git
>> > Initialized empty Git repository in /extra/wireless-dev/.git/
>> > fatal: The remote end hung up unexpectedly
>>
>> Are you sure the above is ".../linux/kernel/gt/linville/..."?
>
> You're right it should be git instead of gt, somewhere in my copying
> strings around I lost the 'i' and wasn't paying attention. That's not
> a very good error message: "fatal: The remote end hung up
> unexpectedly" for a missing repository.
>
It's necessary for security reasons that the git daemon doesn't tell you
*why* it failed though, otherwise attackers could use the git daemon to
browse the existance of files and directories on the remote end.
It could be nice to add "Are you sure $path_to_repo hosts a repository?"
to the message though, which would toss any spelling errors in the users'
face.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-02-13 15:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 19:53 Efficiency of initial clone from server Jon Smirl
2007-02-11 22:53 ` Shawn O. Pearce
2007-02-11 23:25 ` Jon Smirl
2007-02-11 23:51 ` Jon Smirl
2007-02-12 1:38 ` Nicolas Pitre
2007-02-12 2:15 ` Jon Smirl
2007-02-12 3:55 ` Nicolas Pitre
2007-02-12 4:49 ` Shawn O. Pearce
2007-02-12 16:42 ` Nicolas Pitre
2007-02-12 4:16 ` Junio C Hamano
2007-02-12 4:29 ` Jon Smirl
2007-02-12 4:33 ` Junio C Hamano
2007-02-12 4:53 ` Jon Smirl
2007-02-12 5:01 ` Jon Smirl
2007-02-12 5:11 ` Shawn O. Pearce
2007-02-12 5:17 ` Jon Smirl
2007-02-12 15:20 ` Nicolas Pitre
2007-02-12 19:35 ` Theodore Tso
2007-02-12 20:53 ` Junio C Hamano
2007-02-12 21:33 ` Nicolas Pitre
2007-02-13 0:51 ` Jakub Narebski
2007-02-12 5:30 ` Junio C Hamano
2007-02-12 5:55 ` Jon Smirl
2007-02-12 6:08 ` Junio C Hamano
2007-02-12 15:24 ` Jon Smirl
2007-02-12 16:40 ` Jon Smirl
2007-02-12 17:04 ` Shawn O. Pearce
2007-02-12 11:45 ` Johannes Schindelin
2007-02-12 14:31 ` Jon Smirl
2007-02-12 17:06 ` Shawn O. Pearce
2007-02-13 15:03 ` Andreas Ericsson [this message]
2007-02-11 23:29 ` Jon Smirl
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=45D1D32C.1070900@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=junkio@cox.net \
--cc=nico@cam.org \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.