From: Ben Boeckel <ben.boeckel@kitware.com>
To: Brandon Williams <bmwill@google.com>
Cc: git@vger.kernel.org, brad.king@kitware.com
Subject: Re: gitattributes not read for diff-tree anymore in 2.15?
Date: Tue, 5 Dec 2017 14:48:01 -0500 [thread overview]
Message-ID: <20171205194801.GA31721@megas.kitware.com> (raw)
In-Reply-To: <20171205181645.GA159917@google.com>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
On Tue, Dec 05, 2017 at 10:16:45 -0800, Brandon Williams wrote:
> Perfect, thanks!
OK, attached is a shell script which recreates the issue. I haven't been
able to get it to happen without the `GIT_WORK_TREE` and `GIT_INDEX_FILE`
setup involved, so that seems to be important.
I reran the bisect using this script and came up with this commit:
commit be4ca290570f9173db64ea1f925b5b3831c6efed
Author: David Turner <dturner@twosigma.com>
Date: Thu Apr 20 16:41:18 2017 -0400
Increase core.packedGitLimit
<snip>
which seems even less relevant…
Thanks,
--Ben
[-- Attachment #2: diff-tree-break.sh --]
[-- Type: application/x-sh, Size: 933 bytes --]
next prev parent reply other threads:[~2017-12-05 19:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 21:22 gitattributes not read for diff-tree anymore in 2.15? Ben Boeckel
2017-12-04 23:03 ` Brandon Williams
2017-12-05 15:42 ` Ben Boeckel
2017-12-05 18:16 ` Brandon Williams
2017-12-05 19:48 ` Ben Boeckel [this message]
2017-12-05 22:13 ` [PATCH] diff-tree: read the index so attribute checks work in bare repositories Brandon Williams
2017-12-05 22:29 ` Ben Boeckel
2017-12-05 22:31 ` Brandon Williams
2017-12-05 23:13 ` Junio C Hamano
2017-12-05 23:14 ` Stefan Beller
2017-12-06 21:47 ` Brandon Williams
2017-12-05 23:25 ` Eric Sunshine
2017-12-06 22:00 ` Brandon Williams
2017-12-06 22:07 ` Eric Sunshine
2017-12-06 22:02 ` [PATCH v2] " Brandon Williams
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171205194801.GA31721@megas.kitware.com \
--to=ben.boeckel@kitware.com \
--cc=bmwill@google.com \
--cc=brad.king@kitware.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).