On Fri, 24 Aug 2012 11:48:51 -0400, Boggess, Rod wrote: > I'm trying to prevent push/pull when MQ patches are applied. The problem > (so far) is with the push, which triggers when I'm doing a pull. I > started with this in the ini for the repo: > > [hook] > > Preoutgoing.mq-no-push = ! hg qtop > /dev/null 2>&1.
Hi, "hg push" of mq is disallowed by default. So, what you need is to prevent "hg pull". http://mercurial.selenic.com/wiki/MqExtension#Hook_Examples If you're using recent version, you may wish to adopt the phase concept: http://mercurial.selenic.com/wiki/MqExtension#Ensure_patch_queue_changesets_use_secret_Phase With phase, you don't need to put preoutgoing.mq-no-push hook. Regards, > However, the device /dev/null in windows is NUL. When I run this command > from the DOS window, it of course generates an error, which cause the > hook to break. (Or so I thought.) > > > > So, I changed to hook to this: > > > > Preoutgoing.mq-no-push = ! hg qtop > NUL 2>&1 > > > > >From a DOS prompt, this outputs nothing. But when I attempt to pull a > change down from the server, I still get, "abort: preoutgoing.mq-no-push > hook exited with status 1". I don't know if the "2>&1" works in DOS, but > if it doesn't, then I will never report an error result, and this hook > wouldn't prevent a push when it should. Anyone have any suggestions on > how to make this work on Windows? ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
