Please use descriptive messages in your commit logs, this must've been stressed by Fireball at least a dozen times (Sometimes even with consequences). When we have to go over the changelog (Which is textlog-only), what are we supposed to put when we see 10 "Fix a bug" entries? It means we have to check out the log for every revision with such a message, and try to understand the change. Since the log is usually done by non-technical people, this becomes impossible for them.
Best regards, Alex Ionescu
-----Original Message----- From: ros-diffs-bounces@reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of dgorbachev@svn.reactos.org Sent: April-14-07 2:07 PM To: ros-diffs@reactos.org Subject: [ros-diffs] [dgorbachev] 26342: Fix a bug.
Author: dgorbachev Date: Sat Apr 14 22:07:08 2007 New Revision: 26342
URL: http://svn.reactos.org/svn/reactos?rev=26342&view=rev Log: Fix a bug.
Modified: trunk/reactos/ntoskrnl/ps/query.c
Modified: trunk/reactos/ntoskrnl/ps/query.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ps/query.c?rev=263... ============================================================================== --- trunk/reactos/ntoskrnl/ps/query.c (original) +++ trunk/reactos/ntoskrnl/ps/query.c Sat Apr 14 22:07:08 2007 @@ -267,7 +267,7 @@ VmCounters->PeakPagefileUsage = Process->QuotaPeak[2];
/* Set the return length */ - *ReturnLength = sizeof(VM_COUNTERS); + Length = sizeof(VM_COUNTERS); } _SEH_HANDLE {
-
Alex Ionescu