From: Jeff King <peff@peff.net>
Date: Tue, 11 Jan 2011 19:51:07 GMT
Subject: Re: clone breaks replace
Message-ID: <20110111195107.GA18714@sigill.intra.peff.net>
In-Reply-To: <201101112048.57326.j6t@kdbg.org>

On Tue, Jan 11, 2011 at 08:48:57PM +0100, Johannes Sixt wrote:

> On Dienstag, 11. Januar 2011, Jeff King wrote:
> > On Tue, Jan 11, 2011 at 10:24:01AM -0500, Phillip Susi wrote:
> > > Yes, either a new branch or separate historical repository could be
> > > published to pull the original history from, or git would need to pass
> > > the --no-replace-objects flag to git-upload-pack on the server, causing
> > > it to ignore the replace and send the original history.
> >
> > AFAIK, git can't pass --no-replace-objects to the server over git:// (or
> > smart http). You would need a protocol extension.
> 
> Why would you have to? git-upload-pack never looks at replacement objects.

I think you missed the first part of this discussion. Phillip is
proposing that it should, and I am arguing against it.

-Peff