git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Peter Baumann <Peter.B.Baumann@stud.informatik.uni-erlangen.de>,
	git@vger.kernel.org
Subject: Re: Java GIT/Eclipse GIT version 0.1.1
Date: Sat, 29 Jul 2006 00:08:19 -0400	[thread overview]
Message-ID: <20060729040819.GD28128@spearce.org> (raw)
In-Reply-To: <1154145355.26378.35.camel@dv>

Pavel Roskin <proski@gnu.org> wrote:
> On Fri, 2006-07-28 at 23:32 -0400, Shawn Pearce wrote:
> 
> > Hmm.  My website is known to return 200 OK status codes on missing
> > files with HTML pages rather than proper 404 Not Found.  I guess
> > I need to get that fixed.
> 
> Maybe git-http-fetch could treat MIME type text/html like error 404?
> It's not like any valid file git requests can be in HTML format.

This has been discussed to death on the list, mostly due to my pg
repository causing the same error (its on the same server).

The solution turned out to be rather good in my opinion: if an
object is corrupt we log it, and skip to pack downloading.  At the
end the bad object is logged and the user is encouraged to run
git-fsck-objects to verify there's no corrupt objects or objects
which are missing things they point at (e.g. ancestor commits
or trees).

Of course the real solution here is for me to fix my server.  :-)

> > I just compiled and installed `next` (1.4.2.rc1.g802da) and it can
> > clone this repository just fine over HTTP, despite my broken server.
> > So I'm not really sure what is going on.
> 
> Sorry, I was unclear.  I can clone the repository, I was just concerned
> that something was missing from it.

git-http-fetch recommends running git-fsck-objects to be sure,
but yea, usually its complete even though you get the error.

-- 
Shawn.

  reply	other threads:[~2006-07-29  4:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28  6:36 Java GIT/Eclipse GIT version 0.1.1 Shawn Pearce
2006-07-28  6:49 ` Peter Baumann
2006-07-28  7:08   ` Pavel Roskin
2006-07-28  7:23     ` Peter Baumann
2006-07-29  2:10       ` Pavel Roskin
2006-07-29 16:46         ` Peter Baumann
2006-07-29  3:32     ` Shawn Pearce
2006-07-29  3:55       ` Pavel Roskin
2006-07-29  4:08         ` Shawn Pearce [this message]
2006-07-29 10:15 ` Jakub Narebski
2006-07-30 14:55 ` Daniel Barkalow
2006-07-31  4:22   ` Shawn Pearce

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060729040819.GD28128@spearce.org \
    --to=spearce@spearce.org \
    --cc=Peter.B.Baumann@stud.informatik.uni-erlangen.de \
    --cc=git@vger.kernel.org \
    --cc=proski@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).