All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
To: git@vger.kernel.org
Subject: Re: update-index --assume-unchanged doesn't make things go fast
Date: Wed, 25 Jun 2008 19:38:19 +0200	[thread overview]
Message-ID: <g3tvqd$2jj$1@ger.gmane.org> (raw)
In-Reply-To: <32541b130806250944x717cf609x7aa520c77a7c6911@mail.gmail.com>

Avery Pennarun venit, vidit, dixit 25.06.2008 18:44:
...
> 4) My idea is to eventually --assume-unchanged my whole repository,
> then write a cheesy daemon that uses the Win32 dnotify-equivalent to
> watch for files that get updated and then selectively
> --no-assume-unchanged files that it gets notified about.  That would
> avoid the need to ever synchronously scan the whole repo for changes,
> thus making my git-Win32 experience much faster and more enjoyable.
> (This daemon ought to be possible to run on Linux as well, for similar
> improvements on gigantic repositories.  Also note that TortoiseSVN for
> Windows does something similar to track file status updates, so this
> isn't *just* me being crazy.)

Looks like users on slow NFS would profit, too. Hate to say it, but hg 
feels faster on (slow) NFS than git. Yet I use git, for other reasons ;)

Michael

  reply	other threads:[~2008-06-25 17:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25 16:44 update-index --assume-unchanged doesn't make things go fast Avery Pennarun
2008-06-25 17:38 ` Michael J Gruber [this message]
2008-06-25 18:02   ` Avery Pennarun
2008-06-26  8:47     ` Michael J Gruber
2008-06-25 19:30 ` Jakub Narebski
2008-06-25 19:41   ` Junio C Hamano
2008-06-25 19:53   ` Avery Pennarun
2008-06-25 21:35     ` Jakub Narebski
2008-06-26  1:30       ` Avery Pennarun
2008-06-26 11:22 ` Stephen R. van den Berg
2008-06-27 17:01   ` Avery Pennarun
2008-06-27 17:31     ` Jakub Narebski
2008-06-27 17:56       ` Avery Pennarun
2008-06-27 18:09         ` Dana How
2008-06-27 18:51           ` Avery Pennarun
2008-06-28  2:03       ` Junio C Hamano

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='g3tvqd$2jj$1@ger.gmane.org' \
    --to=michaeljgruber+gmane@fastmail.fm \
    --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.
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.