From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: mercurial@selenic.com
Subject: Re: Mercurial's only true "plugin" extension: inotify... and can it be done in Git?
Date: Mon, 10 Mar 2008 19:38:08 +0100 [thread overview]
Message-ID: <200803101938.09300.jnareb@gmail.com> (raw)
In-Reply-To: <200803091459.21354.jnareb@gmail.com>
On Sun, 9 Mar 2008, Jakub Narebski wrote:
> When reading "Distributed Revision Control with Mercurial" 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,
> namely 'inotify' extension.
By the way, when browsing list of available Mercurial extensions
http://www.selenic.com/mercurial/wiki/index.cgi/UsingExtensions
inotify extension was single extension which doesn't have less
or more direct equivalent in Git, or cannot be easy done in Git.
See the table below for details:
Mercurial extension | git equivalent (or proposal)
--------------------+------------------------------------
acl | update-paranoid contrib hook
alias | alias.<cmd> config
bisect | git-bisect
bugzilla | possible as hook
children | possible command, cf. git-name-rev
convert (!) | <possible, would be nice to have>
extdiff | diff.external / GIT_EXTERNAL_DIFF
fetch | git-pull (sic!)
gpg | signed tags
graphlog | <possible, see: tig, git-forest>
hgk (*) | gitk
imerge | see git-mergetool
keyword expansion | check possible gitattributes
mq | Guilt, StGit
notify | post-receive-mail contrib hook,
| default update hook
graphviz | <can be done>
send | <possible, wrapper around git-bundle>
rdiff (!) | <a trick for local repo in GitTips>
localbranch (*) | git-branch, git-checkout
parentRevspec (*) | rev^, rev^1 or rev^2, rev~n
patchbomb | git-send-email
record | git add -i, git commit -i
transplant | git-rebase
win32ext | core.autocrlf config
churn | see git-shortlog
purge | git-clean
cvscommit | see git-cvsexportcommit, git-cvsserver
config | compare git-config
digest | see git-ls-remote for bundle
diffstat | git diff --diffstat, default for git-pull
easy* | see tig
forest | git-submodule
hgcia | CIA hook mentioned on GitWiki
inotify (!!!) |
Footnotes:
==========
(*) Directly inspired by git feature
(!) No direct equivalent, would be quite a work to add
(!!!) No equivalent, don't know if possible
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-03-10 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 13:59 Mercurial's only true "plugin" extension: inotify... and can it be done in Git? Jakub Narebski
2008-03-10 18:38 ` Jakub Narebski [this message]
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=200803101938.09300.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=mercurial@selenic.com \
/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).