git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Mercurial's only true "plugin" extension: inotify... and can it be done in Git?
Date: Sun, 9 Mar 2008 14:59:20 +0100	[thread overview]
Message-ID: <200803091459.21354.jnareb@gmail.com> (raw)

When reading "Distributed Revision Control with Mercurial"[1] to see
how Mercurial differs from Git, in the chapter 14 "Adding functionality 
with extensions" there is description (in section 14.1) of one 
interesting extension (see also [2]), namely 'inotify' extension. 

This extension[3][4] optimises "hg status" command by asking file 
notification daemon about changed files instead of doing stat. I'm not 
sure how useful this extension is: inotify is Linux specific, and Linux 
has fast stat... nevertheless this is one example where extension 
(plug-in) framework shows that it can do more than good scriptability.

I wonder if, and how, such 'extension' could be done with Git...

References:
===========
[1] http://hgbook.red-bean.com
[2] http://www.selenic.com/mercurial/wiki/index.cgi/UsingExtensions
[3] http://hgbook.red-bean.com/hgbookch14.html#x18-31700014.1
[4] http://www.selenic.com/mercurial/wiki/index.cgi/InotifyExtension
-- 
Jakub Narebski
Poland

             reply	other threads:[~2008-03-09 13:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-09 13:59 Jakub Narebski [this message]
2008-03-10 18:38 ` Mercurial's only true "plugin" extension: inotify... and can it be done in Git? Jakub Narebski
2008-03-11  9:42   ` Andreas Ericsson
2008-03-11  9:48     ` Junio C Hamano
2008-03-11 10:20       ` Andreas Ericsson
2008-03-11 10:00     ` Jakub Narebski
     [not found]   ` <e03c8a420803130450y77fd4038h734d80b636fa30a6@mail.gmail.com>
2008-03-15 11:22     ` Jakub Narebski
2008-03-10 19:22 ` Geert Bosch
2008-03-10 22:43   ` Shawn O. Pearce
2008-03-10 22:58     ` J. Bruce Fields

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=200803091459.21354.jnareb@gmail.com \
    --to=jnareb@gmail.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.
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).