# # # patch "releases.xml" # from [41aa27d663a48f94aaf3c62b7d72ce52c3941db9] # to [84baa565561cf2b698bb18eed37e66587a3b136e] # ============================================================ --- releases.xml 41aa27d663a48f94aaf3c62b7d72ce52c3941db9 +++ releases.xml 84baa565561cf2b698bb18eed37e66587a3b136e @@ -1,19 +1,102 @@ - - - - monotone - distributed version control - http://monotone.ca/releases.xml - monotone releases with links to the sources. - en - Fri, 11 Apr 2008 22:50:44 +0000 - - - monotone 0.40 released + + + + monotone - distributed version control + http://monotone.ca/releases.xml + monotone releases with links to the sources. + en + Wed, 3 Sep 2008 21:13:18 +0000 + + monotone 0.41 released Changes
    +
  • 'mtn clone' now takes a branch argument rather than a branch +option which is more what people expect given the fact that +mtn push/pull/sync do not use a branch option either.
  • + +
  • 'mtn automate inventory' will show the birth revision for +any file that has been committed.
  • +
+ +

Bugs fixed

+ +
    +
  • If the options '--db' or '--keydir' were previously +specified for a command which was executed inside a +workspace and one or both option arguments were invalid +(f.e. invalid paths), they were still written to +_MTN/options of the particular workspace. This lead to +errors on any subsequent command which used these +options. This bug is fixed in so far that basic file type +checks are applied on both options, so its no longer +possible to set non-existing paths accidentally or use a +path to a directory as option argument for '--db'.
  • + +
  • If a key clash occurs on a netsync operation, i.e. two +different keys with the same key id are encountered, mtn now +fails cleanly and provides further guidance how to proceed.
  • + +
  • It was previously not possible to clone a branch / database +anonymously; this has been fixed.
  • + +
  • If the client tries to use an unknown key, try to fall back +to anonymous pull instead of failing immediately.
  • + +
  • 'mtn automate identify' was broken in 0.40 when used over +stdio, i.e. the output of the command did not get into the +right output channel; this has been fixed.
  • + +
  • Monotone would produce a warning if executed from the root +directory of a Windows drive; this has been fixed.
  • + +
  • The 'note_commit' hook now returns the new revision id +hex-encoded again - the bug was introduced in 0.40.
  • +
+ +

New features

+ +
    +
  • New 'mtn suspend' command which lets you mark certain +revisions and thus whole branches as discontinued +("suspended") by attaching a special suspend cert to the +revision. All relevant mtn commands (f.e. mtn heads, +mtn ls branches) honor this cert by default. To ignore it, +simply add '--ignore-suspend-certs' to your command line. +Suspended revisions can have children, which are in no +way affected by the cert of their parent, i.e. suspended +development lines or branches can simply be "unsuspended" +by committing to them.
    +This feature was already added in monotone 0.37, but was +forgotten to be mentioned in NEWS back then.
  • + +
  • New 'get_default_command_options' lua hook which lets you +specify default options for a given, triggered command. +Useful f.e. if you always want to have your 'mtn add' +command executed with '-R' / '--recursive'.
  • + +
  • Add 'automate show_conflicts' command.
  • + +
  • Add 'automate get_workspace_root' command.
  • + +
  • Add Lua hooks 'note_netsync_revision_sent', +'note_netsync_cert_sent' and 'note_netsync_pubkey_sent'.
  • + +]]> + + Wed, 3 Sep 2008 21:13:18 +0000 + + + + + monotone 0.40 released + +Changes + +
    • The vim merger has been improved and now uses diff3 to merge non-conflict changes automatically before executing vimdiff.
    • @@ -87,10 +170,10 @@ processing, avoiding conversions and sav Fri, 11 Apr 2008 22:50:44 +0000 - + - - monotone 0.39 released + + monotone 0.39 released Changes @@ -119,7 +202,7 @@ will insist on at least this version. -
    • "emacs" has been removed from the list of dumb terminal types; +
    • "emacs" has been removed from the list of dumb terminal types; tickers should now default to --ticker=count with emacs terminals
    • extensive section on merge conflicts and ways to resolve them @@ -135,14 +218,14 @@ content changes in "file1", but leaves r
    • the path handling of 'mtn revert' was improved and fixed two bugs: now a restricted revert on a node "dir1/file1" reverts only the content changes in "file1", but leaves renames of any of its -ancestor nodes untouched; furthermore, if "dir0/" was renamed to +ancestor nodes untouched; furthermore, if "dir0/" was renamed to "dir1" and "dir1/file1" was dropped, mtn now re-creates file1 at the proper place ("dir1/") and leaves no missing files around because of the non-existing "dir0/".
    • a few changes needed to build with gcc 4.3.
    - +

    New features

      @@ -157,7 +240,7 @@ now runs at least four times faster. -
    • 'automate get_current_revision' which outputs the revision text of +
    • 'automate get_current_revision' which outputs the revision text of changes in the current workspace
    ]]> @@ -165,10 +248,10 @@ changes in the current workspace Mon, 25 Feb 2008 15:55:36 +0000 -
    + - - monotone 0.38 released + + monotone 0.38 released Changes @@ -186,7 +269,7 @@ ensure that any manually merged file isn
  • mtn now checks for your key before a merge action takes place to ensure that any manually merged file isn't lost in an error case
- +

Bugs fixed

    @@ -195,7 +278,7 @@ executed unless the MTN_MERGE environmen
  • mtn read successfully reads revision data, and cert packets again
  • -
  • mtn consistently supports certs with empty values +
  • mtn consistently supports certs with empty values (fixed 'ls certs' and 'read')
@@ -226,10 +309,10 @@ the GFDL. Wed, 12 Dec 2007 21:21:15 +0000 -
+
- - monotone 0.37 released + + monotone 0.37 released @@ -345,4 +428,4 @@ Lua hooks.)
-
+