This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH v12 1/3] Y2038: provide size of default time_t for target architecture


How does this patch differ from version 11, which I already approved?

When a patch is approved that does not depend on other unapproved patches, 
the general expectation is that it will be committed, unless you find some 
other issue with it so you no longer think it's suitable for commit as-is 
and instead want to propose a new changed version.  Then a shorter patch 
series would be posted, omitting the committed patches.

In general, when submitting a revised patch or patch series it's a good 
idea to make clear what has changed from the previous version (this should 
go in the patch submission emails, but not the commit message; the Linux 
kernel convention is that after the commit message you can have a "---" 
line, then any additional information not intended for the commit message, 
such as about changes from previous patch versions, before the patch 
itself).

-- 
Joseph S. Myers
joseph@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]