Issue1283

Title local clone should emit hook events
Priority feature Status chatting
Superseder Nosy List deba, djc, pmezard, tonfa
Assigned To Topics

Created on 2008-09-01.10:43:40 by deba, last changed 2008-09-09.09:42:35 by djc.

Messages
msg7007 (view) Author: djc Date: 2008-09-09.09:42:35
Degrading to feature.
msg6988 (view) Author: deba Date: 2008-09-07.15:52:53
The hgrc manual page says that,

post-<command>
Run after successful invocations of the associated command. The contents of the 
command line are passed as $HG_ARGS and the result code in $HG_RESULT. Hook 
failure is ignored.

pre-<command>
Run before executing the associated command. The contents of the command line 
are passed as $HG_ARGS. If the hook returns failure, the command doesn't execute 
and Mercurial returns the failure code.

Therefore at least pre-clone and post-clone events should be emitted.

By the way, for remote clone (at least for ssh) outgoing events are generated. 
In my opinion, there should not be difference in such case.
msg6915 (view) Author: tonfa Date: 2008-09-02.13:53:16
I don't see an indication in the documentation that some hooks are run on clone.
Only push/pull/update/commit are mentionned.
msg6887 (view) Author: deba Date: 2008-09-01.10:43:39
The local clone does not emit outgoing event, but logically it should. It neither emit pre-clone and
post-clone events.
History
Date User Action Args
2008-09-09 09:42:35djcsetpriority: bug -> feature
nosy: + djc
messages: + msg7007
2008-09-07 15:52:54debasetmessages: + msg6988
2008-09-02 13:53:16tonfasetstatus: unread -> chatting
messages: + msg6915
2008-09-02 13:49:16tonfasetnosy: + tonfa
2008-09-02 06:18:38pmezardsetnosy: + pmezard
2008-09-01 10:43:40debacreate