Message141121
| Author |
sdaoden |
| Recipients |
nadeem.vawda, neologix, pitrou, ronaldoussoren, santoso.wijaya, sdaoden, vstinner |
| Date |
2011年07月25日.20:27:17 |
| SpamBayes Score |
4.522934e-06 |
| Marked as misclassified |
No |
| Message-id |
<20110725202706.GA35353@sherwood.local> |
| In-reply-to |
<CAH_1eM24Y0ADauNB2EJXYw32_g_QpBnC-q-CS7S5oUfY2oym5w@mail.gmail.com> |
| Content |
> Are you willing to update your patch accordingly?
I'm a vain rooster! I've used fullfsync() in 11877-standalone.1.diff!
Sorry for that, haypo. :-/
11877.fullsync-1.diff uses fullsync() and will instead always be
provided when fsync() is available, to which it will fall back if
no special operating system functionality is available.
I really think this is the cleanest solution, because like this
a user can state "i want the strongest guarantees available on
data integrity", and Python does just that.
--Steffen
Ciao, sdaoden(*)(gmail.com)
ASCII ribbon campaign ( ) More nuclear fission plants
against HTML e-mail X can serve more coloured
and proprietary attachments / \ and sounding animations |
|