Skip to content

G
gflags
Commit 313e39e3 authored by Andreas Schuh's avatar Andreas Schuh
Browse files
Options

Add missing name to ChangeLog entry and further format changes.

parent dc9674ee
Show whitespace changes
Inline Side-by-side
Showing with 210 additions and 195 deletions
ChangeLog.txt
View file @ 313e39e3
* Wed Jan 25 2012 Google Inc. <google-gflags@googlegroups.com> -------------------------------------------------------------------
* Wed Jan 25 2012 - Google Inc. <google-gflags@googlegroups.com>
- gflags: version 2.0
- Changed the 'official' gflags email in setup.py/etc - gflags: version 2.0
- Renamed google-gflags.sln to gflags.sln - Changed the 'official' gflags email in setup.py/etc
- Changed copyright text to reflect Google's relinquished ownership - Renamed google-gflags.sln to gflags.sln
- Changed copyright text to reflect Google's relinquished ownership
* Tue Dec 20 2011 Google Inc. <opensource@google.com>
-------------------------------------------------------------------
- google-gflags: version 1.7 * Tue Dec 20 2011 - Google Inc. <opensource@google.com>
- Add CommandLineFlagInfo::flag_ptr pointing to current storage (musji)
- PORTING: flush after writing to stderr, needed on cygwin - google-gflags: version 1.7
- PORTING: Clean up the GFLAGS_DLL_DECL stuff better - Add CommandLineFlagInfo::flag_ptr pointing to current storage (musji)
- Fix a bug in StringPrintf() that affected large strings (csilvers) - PORTING: flush after writing to stderr, needed on cygwin
- Die at configure-time when g++ isn't installed - PORTING: Clean up the GFLAGS_DLL_DECL stuff better
- Fix a bug in StringPrintf() that affected large strings (csilvers)
* Fri Jul 29 2011 Google Inc. <opensource@google.com> - Die at configure-time when g++ isn't installed
- google-gflags: version 1.6 -------------------------------------------------------------------
- BUGFIX: Fix a bug where we were leaving out a required $(top_srcdir) * Fri Jul 29 2011 - Google Inc. <opensource@google.com>
- Fix definition of clstring (jyrki)
- Split up flag declares into its own file (jyrki) - google-gflags: version 1.6
- Add --version support (csilvers) - BUGFIX: Fix a bug where we were leaving out a required $(top_srcdir)
- Update the README for gflags with static libs - Fix definition of clstring (jyrki)
- Update acx_pthread.m4 for nostdlib - Split up flag declares into its own file (jyrki)
- Change ReparseCommandLineFlags to return void (csilvers) - Add --version support (csilvers)
- Some doc typofixes and example augmentation (various) - Update the README for gflags with static libs
- Update acx_pthread.m4 for nostdlib
* Mon Jan 24 2011 Google Inc. <opensource@google.com> - Change ReparseCommandLineFlags to return void (csilvers)
- Some doc typofixes and example augmentation (various)
- google-gflags: version 1.5
- Better reporting of current vs default value (handler) -------------------------------------------------------------------
- Add API for cleaning up of memory at program-exit (jmarantz) * Mon Jan 24 2011 - Google Inc. <opensource@google.com>
- Fix macros to work inside namespaces (csilvers)
- Use our own string typedef in case string is redefined (csilvers) - google-gflags: version 1.5
- Updated to autoconf 2.65 - Better reporting of current vs default value (handler)
- Add API for cleaning up of memory at program-exit (jmarantz)
* Wed Oct 13 2010 Google Inc. <opensource@google.com> - Fix macros to work inside namespaces (csilvers)
- Use our own string typedef in case string is redefined (csilvers)
- google-gflags: version 1.4 - Updated to autoconf 2.65
- Add a check to prevent passing 0 to DEFINE_string (jorg)
- Reduce compile (.o) size (jyrki) -------------------------------------------------------------------
- Some small changes to quiet debug compiles (alexk) * Wed Oct 13 2010 - Google Inc. <opensource@google.com>
- PORTING: better support static linking on windows (csilvers)
- DOCUMENTATION: change default values, use validators, etc. - google-gflags: version 1.4
- Update the NEWS file to be non-empty - Add a check to prevent passing 0 to DEFINE_string (jorg)
- Add pkg-config (.pc) files for libgflags and libgflags_nothreads - Reduce compile (.o) size (jyrki)
- Some small changes to quiet debug compiles (alexk)
* Mon Jan 4 2010 Google Inc. <opensource@google.com> - PORTING: better support static linking on windows (csilvers)
- DOCUMENTATION: change default values, use validators, etc.
- google-gflags: version 1.3 - Update the NEWS file to be non-empty
- PORTABILITY: can now build and run tests under MSVC (csilvers) - Add pkg-config (.pc) files for libgflags and libgflags_nothreads
- Remove the python gflags code, which is now its own package (tansell)
- Clarify that "last flag wins" in the docs (csilvers) -------------------------------------------------------------------
- Comment danger of using GetAllFlags in validators (wojtekm) * Mon Jan 4 2010 - Google Inc. <opensource@google.com>
- PORTABILITY: Some fixes necessary for c++0x (mboerger)
- Makefile fix: $(srcdir) -> $(top_srcdir) in one place (csilvres) - google-gflags: version 1.3
- INSTALL: autotools to autoconf v2.64 + automake v1.11 (csilvers) - PORTABILITY: can now build and run tests under MSVC (csilvers)
- Remove the python gflags code, which is now its own package (tansell)
* Thu Sep 10 2009 Google Inc. <opensource@google.com> - Clarify that "last flag wins" in the docs (csilvers)
- Comment danger of using GetAllFlags in validators (wojtekm)
- google-gflags: version 1.2 - PORTABILITY: Some fixes necessary for c++0x (mboerger)
- PORTABILITY: can now build and run tests under mingw (csilvers) - Makefile fix: $(srcdir) -> $(top_srcdir) in one place (csilvres)
- Using a string arg for a bool flag is a compile-time error (rbayardo) - INSTALL: autotools to autoconf v2.64 + automake v1.11 (csilvers)
- Add --helpxml to gflags.py (salcianu)
- Protect against a hypothetical global d'tor mutex problem (csilvers) -------------------------------------------------------------------
- BUGFIX: can now define a flag after 'using namespace google' (hamaji) * Thu Sep 10 2009 - Google Inc. <opensource@google.com>
* Tue Apr 14 2009 Google Inc. <opensource@google.com> - google-gflags: version 1.2
- PORTABILITY: can now build and run tests under mingw (csilvers)
- google-gflags: version 1.1 - Using a string arg for a bool flag is a compile-time error (rbayardo)
- Add both foo and nofoo for boolean flags, with --undefok (andychu) - Add --helpxml to gflags.py (salcianu)
- Better document how validators work (wojtekm) - Protect against a hypothetical global d'tor mutex problem (csilvers)
- Improve binary-detection for bash-completion (mtamsky) - BUGFIX: can now define a flag after 'using namespace google' (hamaji)
- Python: Add a concept of "key flags", used with --help (salcianu)
- Python: Robustify flag_values (salcianu) -------------------------------------------------------------------
- Python: Add a new DEFINE_bool alias (keir, andrewliu) * Tue Apr 14 2009 - Google Inc. <opensource@google.com>
- Python: Do module introspection based on module name (dsturtevant)
- Fix autoconf a bit better, especially on windows and solaris (ajenjo) - google-gflags: version 1.1
- BUG FIX: gflags_nothreads was linking against the wrong lib (ajenjo) - Add both foo and nofoo for boolean flags, with --undefok (andychu)
- BUG FIX: threads-detection failed on FreeBSD; replace it (ajenjo) - Better document how validators work (wojtekm)
- PORTABILITY: Quiet an internal compiler error with SUSE 10 (csilvers) - Improve binary-detection for bash-completion (mtamsky)
- PORTABILITY: Update deb.sh for more recenty debuilds (csilvers) - Python: Add a concept of "key flags", used with --help (salcianu)
- PORTABILITY: #include more headers to satify new gcc's (csilvers) - Python: Robustify flag_values (salcianu)
- INSTALL: Updated to autoconf 2.61 and libtool 1.5.26 (csilvers) - Python: Add a new DEFINE_bool alias (keir, andrewliu)
- Python: Do module introspection based on module name (dsturtevant)
* Fri Oct 3 2008 Google Inc. <opensource@google.com> - Fix autoconf a bit better, especially on windows and solaris (ajenjo)
- BUG FIX: gflags_nothreads was linking against the wrong lib (ajenjo)
- google-gflags: version 1.0 - BUG FIX: threads-detection failed on FreeBSD; replace it (ajenjo)
- Add a missing newline to an error string (bcmills) - PORTABILITY: Quiet an internal compiler error with SUSE 10 (csilvers)
- (otherwise exactly the same as gflags 1.0rc2) - PORTABILITY: Update deb.sh for more recenty debuilds (csilvers)
- PORTABILITY: #include more headers to satify new gcc's (csilvers)
* Thu Sep 18 2008 Google Inc. <opensource@google.com> - INSTALL: Updated to autoconf 2.61 and libtool 1.5.26 (csilvers)
- google-gflags: version 1.0rc2 -------------------------------------------------------------------
- Report current flag values in --helpxml (hdn) * Fri Oct 3 2008 - Google Inc. <opensource@google.com>
- Fix compilation troubles with gcc 4.3.3 (simonb)
- BUG FIX: I was missing a std:: in DECLARE_string (csilvers) - google-gflags: version 1.0
- BUG FIX: Clarify in docs how to specify --bool flags (csilvers) - Add a missing newline to an error string (bcmills)
- BUG FIX: Fix --helpshort for source files not in a subdir (csilvers) - (otherwise exactly the same as gflags 1.0rc2)
- BUG FIX: Fix python unittest for 64-bit builds (bcmills)
-------------------------------------------------------------------
* Tue Aug 19 2008 * Thu Sep 18 2008 - Google Inc. <opensource@google.com>
- google-gflags: version 1.0rc1 - google-gflags: version 1.0rc2
- Move #include files from google/ to gflags/ (csilvers) - Report current flag values in --helpxml (hdn)
- Small optimizations to reduce binary (library) size (jyrki) - Fix compilation troubles with gcc 4.3.3 (simonb)
- BUGFIX: forgot a std:: in one of the .h files (csilvers) - BUG FIX: I was missing a std:: in DECLARE_string (csilvers)
- Speed up locking by making sure calls are inlined (ajenjo) - BUG FIX: Clarify in docs how to specify --bool flags (csilvers)
- 64-BIT COMPATIBILITY: Use %PRId64 instead of %lld (csilvers) - BUG FIX: Fix --helpshort for source files not in a subdir (csilvers)
- PORTABILITY: fix Makefile to work with Cygwin (ajenjo) - BUG FIX: Fix python unittest for 64-bit builds (bcmills)
- PORTABILITY: fix code to compile under Visual Studio (ajenjo)
- PORTABILITY: fix code to compile under Solaris 10 with CC (csilvers) -------------------------------------------------------------------
* Tue Aug 19 2008 - Google Inc. <opensource@google.com>
* Mon Jul 21 2008 Google Inc. <opensource@google.com>
- google-gflags: version 1.0rc1
- google-gflags: version 0.9 - Move #include files from google/ to gflags/ (csilvers)
- Add the ability to validate a command-line flag (csilvers) - Small optimizations to reduce binary (library) size (jyrki)
- Add completion support for commandline flags in bash (daven) - BUGFIX: forgot a std:: in one of the .h files (csilvers)
- Add -W compile flags to Makefile, when using gcc (csilvers) - Speed up locking by making sure calls are inlined (ajenjo)
- Allow helpstring to be NULL (cristianoc) - 64-BIT COMPATIBILITY: Use %PRId64 instead of %lld (csilvers)
- Improved documentation of classes in the .cc file (csilvers) - PORTABILITY: fix Makefile to work with Cygwin (ajenjo)
- Fix python bug with AppendFlagValues + shortnames (jjtswan) - PORTABILITY: fix code to compile under Visual Studio (ajenjo)
- Use bool instead of int for boolean flags in gflags.py (bcmills) - PORTABILITY: fix code to compile under Solaris 10 with CC (csilvers)
- Simplify the way we declare flags, now more foolproof (csilvers)
- Better error messages when bool flags collide (colohan) -------------------------------------------------------------------
- Only evaluate DEFINE_foo macro args once (csilvers) * Mon Jul 21 2008 - Google Inc. <opensource@google.com>
* Wed Mar 26 Google Inc. <opensource@google.com> - google-gflags: version 0.9
- Add the ability to validate a command-line flag (csilvers)
- google-gflags: version 0.8 - Add completion support for commandline flags in bash (daven)
- Export DescribeOneFlag() in the API - Add -W compile flags to Makefile, when using gcc (csilvers)
- Add support for automatic line wrapping at 80 cols for gflags.py - Allow helpstring to be NULL (cristianoc)
- Bugfix: do not treat an isolated "-" the same as an isolated "--" - Improved documentation of classes in the .cc file (csilvers)
- Update rpm spec to point to Google Code rather than sourceforge (!) - Fix python bug with AppendFlagValues + shortnames (jjtswan)
- Improve documentation (including documenting thread-safety) - Use bool instead of int for boolean flags in gflags.py (bcmills)
- Improve #include hygiene - Simplify the way we declare flags, now more foolproof (csilvers)
- Improve testing - Better error messages when bool flags collide (colohan)
- Only evaluate DEFINE_foo macro args once (csilvers)
* Thu Oct 18 2007 Google Inc. <opensource@google.com>
-------------------------------------------------------------------
- google-gflags: version 0.7 * Wed Mar 26 - Google Inc. <opensource@google.com>
- Deal even more correctly with libpthread not linked in (csilvers)
- Add STRIP_LOG, an improved DO_NOT_SHOW_COMMANDLINE_HELP (sioffe) - google-gflags: version 0.8
- Be more accurate printing default flag values in --help (dsturtevant) - Export DescribeOneFlag() in the API
- Reduce .o file size a bit by using shorter namespace names (jeff) - Add support for automatic line wrapping at 80 cols for gflags.py
- Use relative install path, so 'setup.py --home' works (csilvers) - Bugfix: do not treat an isolated "-" the same as an isolated "--"
- Notice when a boolean flag has a non-boolean default (bnmouli) - Update rpm spec to point to Google Code rather than sourceforge (!)
- Broaden --helpshort to match foo-main.cc and foo_main.cc (hendrie) - Improve documentation (including documenting thread-safety)
- Fix "no modules match" message for --helpshort, etc (hendrie) - Improve #include hygiene
- Improve testing
* Wed Aug 15 2007 Google Inc. <opensource@google.com>
-------------------------------------------------------------------
- google-gflags: version 0.6 * Thu Oct 18 2007 - Google Inc. <opensource@google.com>
- Deal correctly with case that libpthread is not linked in (csilvers)
- Update Makefile/tests so we pass "make distcheck" (csilvers) - google-gflags: version 0.7
- Document and test that last assignment to a flag wins (wan) - Deal even more correctly with libpthread not linked in (csilvers)
- Add STRIP_LOG, an improved DO_NOT_SHOW_COMMANDLINE_HELP (sioffe)
* Tue Jun 12 2007 Google Inc. <opensource@google.com> - Be more accurate printing default flag values in --help (dsturtevant)
- Reduce .o file size a bit by using shorter namespace names (jeff)
- google-gflags: version 0.5 - Use relative install path, so 'setup.py --home' works (csilvers)
- Include all m4 macros in the distribution (csilvers) - Notice when a boolean flag has a non-boolean default (bnmouli)
- Python: Fix broken data_files field in setup.py (sidlon) - Broaden --helpshort to match foo-main.cc and foo_main.cc (hendrie)
- Python: better string serliaizing and unparsing (abo, csimmons) - Fix "no modules match" message for --helpshort, etc (hendrie)
- Fix checks for NaN and inf to work with Mac OS X (csilvers)
-------------------------------------------------------------------
* Thu Apr 19 2007 Google Inc. <opensource@google.com> * Wed Aug 15 2007 - Google Inc. <opensource@google.com>
- google-gflags: version 0.4 - google-gflags: version 0.6
- Remove is_default from GetCommandLineFlagInfo (csilvers) - Deal correctly with case that libpthread is not linked in (csilvers)
- Portability fixes: includes, strtoll, gcc4.3 errors (csilvers) - Update Makefile/tests so we pass "make distcheck" (csilvers)
- A few doc typo cleanups (csilvers) - Document and test that last assignment to a flag wins (wan)
* Wed Mar 28 2007 Google Inc. <opensource@google.com> -------------------------------------------------------------------
* Tue Jun 12 2007 - Google Inc. <opensource@google.com>
- google-gflags: version 0.3
- python portability fix: use popen instead of subprocess (csilvers) - google-gflags: version 0.5
- Add is_default to CommandLineFlagInfo (pchien) - Include all m4 macros in the distribution (csilvers)
- Make docs a bit prettier (csilvers) - Python: Fix broken data_files field in setup.py (sidlon)
- Actually include the python files in the distribution! :-/ (csilvers) - Python: better string serliaizing and unparsing (abo, csimmons)
- Fix checks for NaN and inf to work with Mac OS X (csilvers)
* Mon Jan 22 2007 Google Inc. <opensource@google.com>
-------------------------------------------------------------------
- google-gflags: version 0.2 * Thu Apr 19 2007 - Google Inc. <opensource@google.com>
- added support for python commandlineflags, as well as c++
- gflags2man, a script to turn flags into a man page (dchristian) - google-gflags: version 0.4
- Remove is_default from GetCommandLineFlagInfo (csilvers)
* Wed Dec 13 2006 Google Inc. <opensource@google.com> - Portability fixes: includes, strtoll, gcc4.3 errors (csilvers)
- A few doc typo cleanups (csilvers)
- google-gflags: initial release:
The gflags package contains a library that implements commandline -------------------------------------------------------------------
flags processing. As such it's a replacement for getopt(). It * Wed Mar 28 2007 - Google Inc. <opensource@google.com>
has increased flexibility, including built-in support for C++
types like string, and the ability to define flags in the source - google-gflags: version 0.3
file in which they're used. - python portability fix: use popen instead of subprocess (csilvers)
- Add is_default to CommandLineFlagInfo (pchien)
- Make docs a bit prettier (csilvers)
- Actually include the python files in the distribution! :-/ (csilvers)
-------------------------------------------------------------------
* Mon Jan 22 2007 - Google Inc. <opensource@google.com>
- google-gflags: version 0.2
- added support for python commandlineflags, as well as c++
- gflags2man, a script to turn flags into a man page (dchristian)
-------------------------------------------------------------------
* Wed Dec 13 2006 - Google Inc. <opensource@google.com>
- google-gflags: version 0.1
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment