From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2010, #04; Sat, 10)
Date: Sun, 11 Apr 2010 22:27:36 +0200 [thread overview]
Message-ID: <4BC230B8.4000608@kdbg.org> (raw)
In-Reply-To: <7vr5mmr6ce.fsf@alter.siamese.dyndns.org>
Am 11.04.2010 05:55, 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.
I do see the warning on Windows even though I shouldn't because we always
set st_dev and st_rdev to zero. There's something iffy. Will investigate.
-- Hannes
prev parent reply other threads:[~2010-04-11 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 3:55 What's cooking in git.git (Apr 2010, #04; Sat, 10) Junio C Hamano
2010-04-11 20:27 ` Johannes Sixt [this message]
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=4BC230B8.4000608@kdbg.org \
--to=j6t@kdbg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.