kotovalexarian-likes-github/ruby--ruby
1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
Code Releases Activity

* ext/zlib/zlib.c: Document mtime header behavior with patch by @schneems

Browse source 
Fixes [GH-1129]: https://github.com/ruby/ruby/pull/1129


git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@53785 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This commit is contained in:
zzak 2016-02-09 05:33:35 +00:00
parent d901058900
commit 70d040ddbd
2 changed files with 19 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
ChangeLog
View file

@ -1,3 +1,8 @@
Tue Feb 9 14:32:23 2016 Zachary Scott <zzak@ruby-lang.org>
* ext/zlib/zlib.c: Document mtime header behavior with patch by @schneems
Fixes [GH-1129]: https://github.com/ruby/ruby/pull/1129
Tue Feb 9 13:52:49 2016 Zachary Scott <zzak@ruby-lang.org>
* re.c: Remove deprecated kcode argument from Regexp.new and compile

15
ext/zlib/zlib.c
View file

@ -3221,7 +3221,20 @@ rb_gzfile_set_lineno(VALUE obj, VALUE lineno)
* Document-method: Zlib::GzipWriter#mtime=
*
* Specify the modification time (+mtime+) in the gzip header.
* Using a Fixnum or Integer
* Using a Fixnum or Integer.
*
* Setting the mtime in the gzip header does not effect the
* mtime of the file generated. Different utilities that
* expand the gzipped files may use the mtime
* header. For example the gunzip utility can use the `-N`
* flag which will set the resultant file's mtime to the
* value in the header. By default many tools will set
* the mtime of the expanded file to the mtime of the
* gzipped file, not the mtime in the header.
*
* If you do not set an mtime, the default value will be the time
* when compression started. Setting a value of 0 indicates
* no time stamp is available.
*/
static VALUE
rb_gzfile_set_mtime(VALUE obj, VALUE mtime)