After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 736286 - Clarify g_file_replace behavior with etags
Clarify g_file_replace behavior with etags
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: docs
2.41.x
Other Linux
: Normal minor
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2014-09-08 20:12 UTC by Ross Lagerwall
Modified: 2014-10-30 20:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
doc: Clarify documentation regarding g_file_replace and etags (1.86 KB, patch)
2014-09-08 20:14 UTC, Ross Lagerwall 		committed Details | Review

Description Ross Lagerwall 2014-09-08 20:12:38 UTC 
Clarify that with g_file_replace, a non-NULL etag is only checked if the file already exists.
Comment 1 Ross Lagerwall 2014-09-08 20:14:08 UTC 
Created attachment 285677 [details] [review]
doc: Clarify documentation regarding g_file_replace and etags

Clarify that with g_file_replace, a non-NULL etag is only checked if the
file already exists.
Comment 2 Ross Lagerwall 2014-10-28 17:20:59 UTC 
Ping?
Comment 3 Alexander Larsson 2014-10-30 19:24:40 UTC 
Review of attachment 285677 [details] [review]:

I'm not sure that this is the best behaviour, but it is indeed how it works now, and I don't think we can change it. So, ACK.
Comment 4 Ross Lagerwall 2014-10-30 20:20:02 UTC 
Pushed to master as 0728e62be8bf247f9d097822efd26312367ff133. Thanks for the review!