From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2010, #05; Wed, 14)
Date: Thu, 15 Apr 2010 09:01:54 +0200 [thread overview]
Message-ID: <4BC6B9E2.5080202@viscovery.net> (raw)
In-Reply-To: <7vy6gpmwr4.fsf@alter.siamese.dyndns.org>
Am 4/15/2010 1:37, schrieb Junio C Hamano:
> * 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
next prev parent reply other threads:[~2010-04-15 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 23:37 What's cooking in git.git (Apr 2010, #05; Wed, 14) Junio C Hamano
2010-04-15 3:39 ` Ramkumar Ramachandra
2010-04-15 7:01 ` Johannes Sixt [this message]
2010-04-18 23:12 ` Nick Edelen
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=4BC6B9E2.5080202@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).