From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Robin Rosenberg <robin.rosenberg@dewire.com>,
Kjetil Barvik <barvik@broadpark.no>,
Linus Torvalds <torvalds@linux-foundation.org>,
Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
Git Mailing List <git@vger.kernel.org>,
spearce@spearce.org
Subject: Re: [PATCH] Add core.trustlowlevelstat for diffs in dev,ino,uid and gid
Date: Mon, 15 Mar 2010 08:41:04 +0100 [thread overview]
Message-ID: <81b0412b1003150041n5938556bqc127939622bfdb57@mail.gmail.com> (raw)
In-Reply-To: <7v1vfm9iyp.fsf@alter.siamese.dyndns.org>
On Mon, Mar 15, 2010 at 07:50, Junio C Hamano <gitster@pobox.com> wrote:
> Robin Rosenberg <robin.rosenberg@dewire.com> writes:
>
>> Did something pop up that I don't know of that prevented inclusion of this
>> patch, other than the NSEC option, or will it do if just refresh the patch?
>
> I think all of us liked the general direction, and also all of us agreed
> that we would want to keep NSEC support that was removed by Linus's patch.
>
> Nobody had time or inclination to update the patch to implement the
> consensus (I still had the thread in my inbox, by the way). So "just
> refresh the patch" would be the necessary first step.
There is an awful lot of "trust-something" variables. Maybe they can be
consolidated into a bitmask/bitfields? And a config option taking a list of
filesystem features which can be trusted for a good measure (preserving
old "trust_something" options, of course).
prev parent reply other threads:[~2010-03-15 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 10:55 [PATCH] Add core.trustlowlevelstat for diffs in dev,ino,uid and gid Robin Rosenberg
2009-04-26 11:06 ` Robin Rosenberg
2009-04-26 12:06 ` [PATCH 1/2] Silence diffs due to use by non-C code Robin Rosenberg
2009-04-26 18:38 ` [PATCH] Add core.trustlowlevelstat for diffs in dev,ino,uid and gid Junio C Hamano
2009-04-26 19:25 ` Linus Torvalds
2009-04-26 22:02 ` Robin Rosenberg
2009-04-27 6:55 ` Junio C Hamano
2009-04-27 15:00 ` Linus Torvalds
2009-04-27 15:58 ` Kjetil Barvik
2010-03-14 20:51 ` Robin Rosenberg
2010-03-15 6:50 ` Junio C Hamano
2010-03-15 7:41 ` Alex Riesen [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=81b0412b1003150041n5938556bqc127939622bfdb57@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=barvik@broadpark.no \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robin.rosenberg.lists@dewire.com \
--cc=robin.rosenberg@dewire.com \
--cc=spearce@spearce.org \
--cc=torvalds@linux-foundation.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.
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).