# # # patch "NEWS" # from [1278129541697d55743c7237da0db78ff2d92856] # to [2dc09a234aa2015751bd65a20ad679fcdc0e1fe0] # ============================================================ --- NEWS 1278129541697d55743c7237da0db78ff2d92856 +++ NEWS 2dc09a234aa2015751bd65a20ad679fcdc0e1fe0 @@ -15,8 +15,8 @@ xxx xxx xx xx:xx:xx UTC 2010 text to be passed to the editor to edit a commit. Existing hooks that override the default hook will need to be changed to work properly. - - The long date/time format used by 'status', 'commit' and 'log' must be - sufficient to preserve a date through a formatting and parsing + - The long date/time format used by 'status', 'commit' and 'log' must + be sufficient to preserve a date through a formatting and parsing cycle. The 'status' command now checks for this and warns if the format is unsuitable and 'commit' will refuse to operate with an unsuitable format. @@ -25,11 +25,19 @@ xxx xxx xx xx:xx:xx UTC 2010 with the new information displayed by 'commit' so that all three commands display revisions similarly. - - The 'setup' as well as the 'clone' command check if a managed default - database exists and if not create one - in case no database option is - given either as command line or workspace option to the command - (see below for more information on the new management features). + - The 'setup' as well as the 'clone' command check if no managed default + database exists and if no database is given either as command line + or as workspace option and eventually create a new default database + outside of the bookkeeping directory of the new workspace (see below + for more information on the new management features). + - The output of monotone diff has changed to use /dev/null as the source + for added files and as the target for deleted files. This is + compatible with patch(1) and will cause it to add and delete files + where appropriate. As part of this change diff will now include the + removed contents of deleted files which were omitted in earlier + versions of monotone. + - Monotone will only warn about bad certs if there are not also matching trusted certs. So if someone commits a bad branch cert, monotone will only warn about that bad cert until someone else approves that @@ -38,25 +46,18 @@ xxx xxx xx xx:xx:xx UTC 2010 - 'db check' now checks for errors in the branch heads cache, and 'db regenerate_caches' fixes them. - - The output of the Lua functions print() and io.write() is - now redirected to the standard progress message stream of - monotone. See chapter 6.3 in the documentation for details. + - The output of the Lua functions print() and io.write() is now + redirected to the standard progress message stream of monotone. + See chapter 6.3 in the documentation for details. - - The output of monotone diff has changed to use /dev/null as the source - for added files and as the target for deleted files. This is - compatible with patch(1) and will cause it to add and delete files - where appropriate. As part of this change diff will now include the - removed contents of deleted files which were omitted in earlier - versions of monotone. - New features - Monotone has now database management capabilities: If you place your - databases in one or more specific locations (defaults to + databases in one or more specific locations (defaults to %APPDIR%/monotone/databases on Windows and $HOME/.monotone/databases - on Linux, configurable by a hook), it is able to discover these databases - and access them only by giving the (base) name of their filename, - for example ":my-database.mtn". + on Linux, configurable by a hook), it is able to discover these + databases and access them only by giving the (base) name of their + filename, for example ":my-database.mtn". You can also directly create new databases in the first found default location by issuing 'mtn db init -d ":my-database.mtn". @@ -64,13 +65,13 @@ xxx xxx xx xx:xx:xx UTC 2010 Some commands, like 'setup' and 'clone' automatically fall back to a default database (":default.mtn", also configurable by a hook) if no database option is explicitely given. - - Additionally monotone remembers checked out workspaces for every + + Additionally, monotone remembers checked out workspaces for every managed database and displays these "known" registered paths together with other information in the new 'list databases' command (closes monotone bug #8916). - - A set of management commands - 'register_workspace', + - A set of accompanying management commands - 'register_workspace', 'unregister_workspace' and 'cleanup_workspace_list' - to handle moved or removed workspaces for managed databases have been added. @@ -82,14 +83,14 @@ xxx xxx xx xx:xx:xx UTC 2010 get_default_command_options(cmd) hook in your monotonerc (fixes monotone bug #17878). - - New command 'undrop' which undoes a 'drop' done by mistake + - New command 'undrop' which undoes a 'drop' done by mistake (fixes monotone bug #13604). - New automation command 'update' which behaves identical to the normal 'update' command. - 'ls tags' now outputs the branch name(s) a tagged revision is on. - The revision id is shortened to the first 10 characters to get some + The revision id is shortened to the first ten characters to get some more space for this (fixes monotone bug #12773). - Default include and exclude patterns are now remembered per server. @@ -139,7 +140,7 @@ xxx xxx xx xx:xx:xx UTC 2010 directory if the target directory "." points to a workspace (fixes monotone bug #29927). - - The commands in monotone's help output are now sorted alphabetically + - The commands in monotone's help output are now sorted alphabetically. - monotone on Windows will now have a non-zero exit code when interrupted (^C). This was broken in 0.47 when it was fixed to not