monotone-commits-nodiffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-commits-nodiffs] Revision 7eb4688b418e6ea3b78ec05cc03fd498e5f7


From: monotone
Subject: [Monotone-commits-nodiffs] Revision 7eb4688b418e6ea3b78ec05cc03fd498e5f70dec
Date: Wed, 28 Feb 2007 22:05:14 +0100

-----------------------------------------------------------------
Revision: 7eb4688b418e6ea3b78ec05cc03fd498e5f70dec
Ancestor: 5a48beac7cb9a305078ab250831a4a33deaa3f72
Author: address@hidden
Date: 2007-02-28T20:10:22
Branch: net.venge.monotone

Modified files:
        configure.ac tester.cc

ChangeLog: 

        * configure.ac: Add putenv and unsetenv to AC_CHECK_FUNCS.
        * tester.cc: Delete the existing definitions of setenv and
          unsetenv, since they collide with existing definitions on
          platforms where they exist.  Add two new functions, set_env, and
          unset_env, that wrap up platform-specific behaviour and give us
          the behavour we need.
          (set_env) Implemented using SetEnvironmentVariable on Win32,
          setenv where we HAVE_SETENV, putenv where we HAVE_PUTENV, and
          #errors out elsewhere for now.
          (unset_env): Use SetEnvironmentVariable on Win32, unsetenv where
          we HAVE_UNSETENV, and #errors out elsewhere for now.  This can
          be implemented using putenv("FOO=") or setenv("FOO", NULL, 1) or
          using similar non-standard hacks on some platforms, but I
          haven't done this yet--we'll cross that bridge when we come to
          it.


monotone --db={your.database} diff 
--revision=5a48beac7cb9a305078ab250831a4a33deaa3f72 
--revision=7eb4688b418e6ea3b78ec05cc03fd498e5f70dec
----------------------------------------------------------------------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]