"Philip M. Gollucci" <[EMAIL PROTECTED]> writes:

>>  #define APREQ_MINOR_VERSION       1
>>   /** patch level */
>> -#define APREQ_PATCH_VERSION       1
>> +#define APREQ_PATCH_VERSION       2
>
> speaking of which shouldn't the patchlevel be at 4 at this point ?
> I'm probably not grasping how apreq is using this though.

The rules are simple:

The patch version should get bumped whenever a commit 
modifies a library/*.c file.  The minor version gets
bumped, and the patch version zeroed, whenever a commit
modifies an include/*.h file.

I wrote some of this down in FAQ.pod.

-- 
Joe Schaefer

Reply via email to