# # # patch "NEWS" # from [bccaa0de110574ab864097d2f71c902ef428c63e] # to [8a9cb2bd6e15e3717f0eb627cea6d742dfa76c52] # ============================================================ --- NEWS bccaa0de110574ab864097d2f71c902ef428c63e +++ NEWS 8a9cb2bd6e15e3717f0eb627cea6d742dfa76c52 @@ -4,12 +4,6 @@ xxx xxx xx xx:xx:xx UTC 2010 Changes - - The 'setup' command now creates a new internal database if no - database is given either as command line or workspace option. - - - 'db check' now checks for errors in the branch heads cache, - and 'db regenerate_caches' fixes them. - - Much more information is now passed to the editor when composing a commit message for a new revision. The Author, Date, Branch and Changelog values may now all be changed directly in the editor @@ -31,28 +25,44 @@ xxx xxx xx xx:xx:xx UTC 2010 with the new information displayed by 'commit' so that all three commands display revisions similarly. - - 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 'setup' command now creates a new internal database if no + database is given either as command line or workspace option. - 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 - revision into the same branch. + revision into the same branch (fixes monotone bug #8033). + - '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. + New features - - New automation command 'update' which behaves identical to - the normal 'update' command. - - Many commands that change the heads of a branch (approve, disapprove, pull, merge, etc) can now take an option "--update". If run from a workspace which is based on a head of the branch and has no local changes, this option makes these commands update that workspace to the new head. If you always want this behavior, you can define the get_default_command_options(cmd) - hook in your monotonerc. + hook in your monotonerc (fixes monotone bug #17878). + - 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 + more space for this (fixes monotone bug #12773). + + - Default include and exclude patterns are now remembered per server. + This means that you can have for example one server that you sync + everything to, and one that you only sync some branches to, and you + don't have to worry about forgetting to give the include pattern and + accidentally trying to sync everything to the second server. + - A new Lua extension function change_workspace(directory) has been added. This should be most useful for custom commands which need to work on multiple workspaces from the same monotone instance. @@ -61,29 +71,25 @@ xxx xxx xx xx:xx:xx UTC 2010 function available since 0.47, which can be used to let a monotone server exit gracefully instead of having to be killed. - - Default include and exclude patterns are now remembered per server. - This means that you can have for example one server that you sync - everything to, and one that you only sync some branches to, and you - don't have to worry about forgetting to give the include pattern and - accidentally trying to sync everything to the second server. - Bugs fixed - A regression in 0.47 prevent successful execution of push / pull / sync over pipes (Debian bug 574512); this has been fixed. - monotone no longer saves changed options from the command line back - to _MTN/options in case the command execution was unsuccessful. + to _MTN/options in case the command execution was unsuccessful + (fixes monotone bug #22928). + - When monotone reads packets from files, like f.e. keys in a directory + given by the --keydir option, and these files are large and do + not contain packet data at all, monotone no longer uses an excessive + amount of time and memory to figure this out + (fixes monotone bug #28799). + - The 'log' command no longer crashes if it is executed in a workspace whose parent revision(s) do not exist in the specified database (fixes monotone bug #29677). - - In 0.46, spurious network disconnects could occur when transferring - sufficiently large items (files, diffs, revisions). This was fixed - in 0.47 but not noted in the release notes at that time - (fixes monotone bug #28991). - - 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 throw an exception on being interrupted. @@ -99,6 +105,11 @@ xxx xxx xx xx:xx:xx UTC 2010 bug' on 'merge', you can fix it by running 'mtn db regenerate_caches'. + - In 0.46, spurious network disconnects could occur when transferring + sufficiently large items (files, diffs, revisions). This was fixed + in 0.47 but not noted in the release notes at that time + (fixes monotone bug #28991). + Other - Support for the diffuse merger (http://diffuse.sourceforge.net)