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

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

[Monotone-commits-diffs] Revision 55dda3948794df463b5aaf38dc8afe34f866f2


From: monotone
Subject: [Monotone-commits-diffs] Revision 55dda3948794df463b5aaf38dc8afe34f866f29b
Date: Tue, 29 Apr 2008 20:06:08 +0200

-----------------------------------------------------------------
Revision: 55dda3948794df463b5aaf38dc8afe34f866f29b
Ancestor: ce6ad7f14d45136e6185d163a430f45d2f4ebec0
Author: Richard Levitte <address@hidden>
Date: 2008-04-29T17:26:40
Branch: net.venge.monotone.commit_without_-b

Modified files:
        cmd_ws_commit.cc options_list.hh work.cc

ChangeLog: 

General change to have the 'mtn branch' command generate a new line in
_MTN/options called "newbranch" which describes the future branch to
commit to.  We might want to think about other commands that could use
this, such as 'mtn disapprove'.

        * cmd_ws_commit.cc (revision_summary,
        get_log_message_interactively): Handle the case when there is
        a newbranch that differs from the current branch.
        (CMD(branch)): Changes to display the move from old to new
        branch, as well as to verify and store a change of branch with
        this new format.
        (CMD(commit)): Handle the newbranch setting.
        * options_list.hh: Add the newbranchname as a hidden option.
        * work.cc (read_options_file, workspace::get_ws_options,
        workspace::get_database_option, workspace::set_ws_options,
        workspace::print_ws_option): Handle the newbranch option.
        (write_options_file): Handle newbranch as well, but NEVER
        write it if it has the same value as the branch option.

Attachment: txtpEOh_QgGsO.txt
Description: Diff [ce6ad7f14d45136e6185d163a430f45d2f4ebec0] -> [55dda3948794df463b5aaf38dc8afe34f866f29b]


reply via email to

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