Re: What's cooking in git.git (Apr 2010, #05; Wed, 14)

From: Johannes Sixt <j.sixt@viscovery.net>
Date: Apr 15, 2010, 07:01 UTC
Message-ID: <4BC6B9E2.5080202@viscovery.net>
In-Reply-To: <7vy6gpmwr4.fsf@alter.siamese.dyndns.org>

Am 4/15/2010 1:37, schrieb Junio C Hamano:

Show 11 quoted lines

> * ld/discovery-limit-to-fs (2010-04-04) 6 commits
>  - write-index: check and warn when worktree crosses a filesystem boundary
>   (merged to 'next' on 2010-04-07 at 11ea09a)
>  + Rename ONE_FILESYSTEM to DISCOVERY_ACROSS_FILESYSTEM
>  + GIT_ONE_FILESYSTEM: flip the default to stop at filesystem boundaries
>  + Add support for GIT_ONE_FILESYSTEM
>  + truncate cwd string before printing error message
>  + config.c: remove static keyword from git_env_bool()
> 
> The tip one is a bit iffy; the whole series changes behaviour in a corner
> case, and is not a 1.7.1 material.

The problem I reported after your previous announcement (that I always see the warning on Windows) was a false alarm. Appearently, I still had some random st_dev values recorded in the index for some old files, like Documentation/RelNotes-1.5.4.*, and it went away after I rebuilt the index.

-- Hannes