git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: David Lang <david@lang.hm>
Cc: "Ondřej Bílka" <neleai@seznam.cz>,
	"Dennis Luehring" <dl.soluz@gmx.net>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: question about: Facebook makes Mercurial faster than Git
Date: Mon, 10 Mar 2014 16:22:08 -0400	[thread overview]
Message-ID: <CACPiFC+yjwakzC-0Z=Asuy6SJAxg=pHv4mis_AP_qKVHkpk1Ag@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1403101053120.20306@nftneq.ynat.uz>

On Mon, Mar 10, 2014 at 1:56 PM, David Lang <david@lang.hm> wrote:
> there's also the issue of managed vs generated files, if you update the
> mtime all the way up the tree because a source file was compiled and a
> binary created, that will quickly defeat the value of the recursive mime.

I think this points us again to an inotify-based strategy, where git
can put an event listener daemon which registers just the watchers it
needs, and filters the events on its own conditions.

The kernel and fs have no good way of knowing about this stuff.

cheers,


m
-- 
 martin.langhoff@gmail.com
 -  ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 ~ http://docs.moodle.org/en/User:Martin_Langhoff

  reply	other threads:[~2014-03-10 20:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 10:07 question about: Facebook makes Mercurial faster than Git Dennis Luehring
2014-03-10 10:13 ` David Lang
2014-03-10 17:51   ` Ondřej Bílka
2014-03-10 17:56     ` David Lang
2014-03-10 20:22       ` Martin Langhoff [this message]
2014-03-11 14:23       ` Ondřej Bílka
2014-03-10 11:28 ` demerphq
2014-03-10 11:42   ` Dennis Luehring
2014-03-10 12:10     ` Johan Herland
2014-03-10 14:48       ` Michael Haggerty
2014-03-10 14:18     ` Karsten Blees
2014-03-14 12:58   ` Duy Nguyen

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='CACPiFC+yjwakzC-0Z=Asuy6SJAxg=pHv4mis_AP_qKVHkpk1Ag@mail.gmail.com' \
    --to=martin.langhoff@gmail.com \
    --cc=david@lang.hm \
    --cc=dl.soluz@gmx.net \
    --cc=git@vger.kernel.org \
    --cc=neleai@seznam.cz \
    /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).