git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: Nicholas Clark <nick@ccl4.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Perl 5 Porters <perl5-porters@perl.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: The Reposithon!  Take 2 [URL FIX]
Date: Tue, 18 Dec 2007 01:00:43 +1300	[thread overview]
Message-ID: <476664EB.5030500@vilain.net> (raw)
In-Reply-To: <20071217115450.GR23703@plum.flirble.org>

Nicholas Clark wrote:
> On Tue, Dec 18, 2007 at 12:48:26AM +1300, Sam Vilain wrote:
>> Nicholas Clark wrote:
>>> error: Could not interpret The page was, like, not found and stuff. as something to pull
>>>
>>>
>>>                            ^ random capitalisation or missing punctuation
>>>                                          ^ slang interjection
>>>                                                          ^ slang interjection
>>>                                                                     ^ missing capitalisation
>>>
>> I've never had my server 404 message
>>
>>   http://utsl.gen.nz/err/404.html
>>
>> So well critiqued!  Thanks!  :-)
>>
>> Hopefully all the pull problems should be sorted now.
> 
> I remain unhappy that git does not tell me that it's reporting a 404 error.
> 404 makes sense in any language. What the server admin chooses as the
> accompanying page may well not, although usually it would be because he or
> she chooses to make it report errors in the local language.

meh.  look, actually tell you what my little web server is returning the
wrong error HTTP response code.  Which is a pretty stupid
misconfiguration and not one you'd see very often.  So the data gets a
little further in before it is noticed to be wrong.

The error message isn't the best, no.

Junio, any chance of this going in?

Subject: Clarify error response from 'git fetch' for bad responses

This error message prints the reponse from the server at this point.
Label it as such in the output.
---
 walker.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/walker.c b/walker.c
index 397b80d..adc3e80 100644
--- a/walker.c
+++ b/walker.c
@@ -274,7 +274,7 @@ int walker_fetch(struct walker *walker, int targets, char **target,
 
 	for (i = 0; i < targets; i++) {
 		if (interpret_target(walker, target[i], &sha1[20 * i])) {
-			error("Could not interpret %s as something to pull", target[i]);
+			error("Could not interpret response from server '%s' as something to pull", target[i]);
 			goto unlock_and_fail;
 		}
 		if (process(walker, lookup_unknown_object(&sha1[20 * i])))

       reply	other threads:[~2007-12-17 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47664617.9010106@vilain.net>
     [not found] ` <4766582F.4030207@vilain.net>
     [not found]   ` <20071217111433.GN23703@plum.flirble.org>
     [not found]     ` <4766620A.6050704@vilain.net>
     [not found]       ` <20071217115450.GR23703@plum.flirble.org>
2007-12-17 12:00         ` Sam Vilain [this message]
2007-12-17 18:00           ` The Reposithon! Take 2 [URL FIX] Junio C Hamano
2007-12-17 18:03             ` Nicholas Clark

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=476664EB.5030500@vilain.net \
    --to=sam@vilain.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nick@ccl4.org \
    --cc=perl5-porters@perl.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).