lostwages/templates/en developer-cheatsheet.te ...

[Jeremy Newman]

ChangeSet ID:	22071
CVSROOT:	/opt/cvs-commit
Module name:	lostwages
Changes by:	[e-mail]	2006/01/03 15:57:14

Modified files:
    templates/en   : developer-cheatsheet.template

Log message:
    Neil Skrypuch 
    Fix config file reference

Patch: http://cvs.winehq.org/patch.py?id=22071

Old revision  New revision  Changes     Path
 1.5           1.6           +4 -3       lostwages/templates/en/developer-cheatsheet.template

Index: lostwages/templates/en/developer-cheatsheet.template
diff -u -p lostwages/templates/en/developer-cheatsheet.template:1.5 lostwages/templates/en/developer-cheatsheet.template:1.6
--- lostwages/templates/en/developer-cheatsheet.template:1.5	3 Jan 2006 21:57:14 -0000
+++ lostwages/templates/en/developer-cheatsheet.template	3 Jan 2006 21:57:14 -0000
@@ -71,9 +71,10 @@
         aren't sure what's going wrong. It shows you each call into
         and out of Wine modules at the DLL boundaries. This includes
         calls between Wine DLLs: for instance, from GDI32 to
-        KERNEL32. Investigate the RelayInclude and RelayExclude keys
-        in the [Debug] section if you're being overwhelmed by certain
-        functions. A good initial value for RelayExclude is:<p>
+        KERNEL32. Investigate the RelayInclude and RelayExclude string
+        values in [HKCU\Software\Wine\Debug] if you're being
+        overwhelmed by certain functions. A good initial value for
+        RelayExclude is:<p>

<code> RtlEnterCriticalSection;RtlLeaveCriticalSection;_EnterSysLevel;_LeaveSysLevel;
         _CheckNotSysLevel;RtlAllocateHeap;RtlFreeHeap;LOCAL_Lock;LOCAL_Unlock