Re: What's cooking in git.git (Jan 2017, #04; Mon, 23)

From: Jeff King <peff@peff.net>
Date: Jan 25, 2017, 17:39 UTC
Message-ID: <20170125173958.pg546a6w33dirp5k@sigill.intra.peff.net>
In-Reply-To: <alpine.DEB.2.20.1701251800120.3469@virtualbox>

On Wed, Jan 25, 2017 at 06:01:11PM +0100, Johannes Schindelin wrote:

Show 6 quoted lines

> > Looks like "mv" prompts and then fails to move the file (so we get the
> > dangling blob for the source blob, and fsck doesn't report failure
> > because we didn't actually corrupt the destination blob).
> 
> IIRC I had similar problems years ago, on a machine where the
> administrator defined mandatory aliases, including mv="mv -i".

Yeah, that was my first thought, too. But this should be a non-interactive shell, which would generally avoid loading rc files. I think there are some exceptions, though (e.g., setting ENV or BASH_ENV). Loading aliases like "mv -i" for non-interactive shells seems somewhat insane to me. But whatever the cause, I think the workaround I posted is easy enough to do.

-Peff