Lines Matching +full:release +full:- +full:please +full:- +full:- +full:branches +full:- +full:- +full:main
1 [](https://travis-ci.org/gfla…
8 ----------------
12 This maintenance release improves lives of Bazel users (no more "config.h" leaking into global incl…
18 Please report any further issues with this release using the GitHub issue tracker.
22 ------------
26 This maintenance release primarily fixes build issues on Windows and
29 Please report any further issues with this release using the GitHub issue tracker.
33 ----------------
37 This release adds support for use of the gflags library as external dependency
39 or [pkg-config](https://www.freedesktop.org/wiki/Software/pkg-config/).
40 One new minor feature is added in this release: when a command flag argument
45 Memory leaks reported by valgrind should be resolved by this release.
46 This release fixes build errors with MS Visual Studio 2015.
48 Please report any further issues with this release using the GitHub issue tracker.
52 -------------
56 This release completes the namespace change fixes. In particular,
57 it restores binary ABI compatibility with release version 2.0.
67 This release also marks the complete move of the gflags project
72 Please report any further issues using the GitHub issue tracker.
76 -------------
80 This release fixes a few bugs in the configuration of gflags\_declare.h
88 -------------
97 This release compiles with all major compilers without warnings and passed
102 repository such that it can be used as Git submodule by projects. The main
107 platforms, please reference the issue number as
110 [Git branching model](http://nvie.com/posts/a-successful-git-branching-model/)
118 ---------------
122 executed on non-Unix platforms and splitting them up into separate CTest tests.
125 [cmake-migration](https://github.com/schuhschuh/gflags/tree/cmake-migration) branch.
129 -------------
136 I believe that the strengths of [Git](http://git-scm.com/) will allow for better community collabor…
139 Git's lightweight feature branches will also provide the right tool for more
151 Please continue to report any issues with gflags on Google Code. The GitHub project will
157 [cmake-migration](https://github.com/schuhschuh/gflags/tree/cmake-migration)
162 ---------------
166 The `google-gflags` project has been renamed to `gflags`. I
183 ---------------
185 The `google-gflags` Google Code page has been renamed to
194 ----------------
196 I've just released gflags 1.7. This is a minor release; the major
199 very long --help strings, and some other minor [changes](ChangeLog.txt).
202 ------------
204 I've just released gflags 1.6. The major new feature in this release
205 is support for setting version info, so that --version does something
214 There's also a procedural change with this release: I've changed the
215 internal tools used to integrate Google-supplied patches for gflags
216 into the opensource release. These new tools should result in more
221 See the [ChangeLog](ChangeLog.txt) for a full list of changes for this release.
224 ---------------
226 I've just released gflags 1.5. This release has only minor changes
227 from 1.4, including some slightly better reporting in --help, and
228 an new memory-cleanup function that can help when running gflags-using
234 [ChangeLog](ChangeLog.txt) for a full list of changes for this release.
237 ---------------
239 I've just released gflags 1.4. This release has only minor changes
245 --------------
248 all tests pass. I **really** never thought non-unix-y Windows folks
252 into its own library, [python-gflags](http://code.google.com/p/python-gflags).
257 -----------------
261 never thought Windows folks would want unix-style command-line flags,
265 The other changes are minor, such as support for --htmlxml in the
269 -------------
278 libgflags.so, but the deb file created libgoogle-gflags.so. I have
281 change as well. Please let me know (at
282 [[mailto:google-gflags@googlegroups.com](mailto:google-gflags@googlegroups.com)
283 google-gflags@googlegroups.com]) if this causes problems for you --
286 (libgoogle-gflags.so -> libgflags.so), but that is beyond my knowledge
290 let me know. I'm excited to finally have 64-bit package files, but
294 --------------
299 `/usr/include/gflags`. While I have backwards-compatibility
300 forwarding headeds in place, please rewrite existing code to say
311 --help` to see the flags). If you have feedback as to whether the
313 non-backwards-compatible change, send mail to
314 `google-gflags@googlegroups.com`!
317 commandline-completion of help flags. See the [ChangeLog](ChangeLog.txt)
320 If I don't hear any bad news for a few weeks, I'll release 1.0-final.