monotone - Bugs: bug #13597, monotone update -b newbranch...
You are not allowed to post comments on this tracker with your current authentication level.
bug #13597: monotone update -b newbranch exhibits incorrect behaviour
Submitter: | None | ||
Submitted: | Fri 01 Jul 2005 01:33:48 PM UTC | ||
Category: | working copy | Severity: | 3 - Normal |
Item Group: | incorrect behavior | Status: | Fixed |
Privacy: | Public | Assigned to: | stephen_leake |
Open/Closed: | Closed | ||
mtn version --full: | monotone 0.19 (base revision: 168adf9537ff136c9b7fe7faad5991f92859390d)
|
Sun 09 May 2010 10:13:25 PM UTC, comment #5: |
Stephen Leake <stephen_leake> |
Sun 09 May 2010 09:56:56 PM UTC, comment #4: Hrm... whats the actual issue here? If I switch the branch from A to B with commit -b B, _MTN/options properly contains B as branch after the commit. Is this maybe some weird local problem, Stephen, or do I get something wrong? |
Thomas Keller <tommyd> |
Sun 09 May 2010 02:02:26 PM UTC, comment #3: continuing the same sequence:
|
Stephen Leake <stephen_leake> |
Sun 09 May 2010 01:55:31 PM UTC, comment #2: I take it back. Consider this sequence:
|
Stephen Leake <stephen_leake> |
Sun 09 May 2010 11:10:25 AM UTC, comment #1: Fixed in current mtn; see the various tests/update* |
Stephen Leake <stephen_leake> |
Fri 01 Jul 2005 01:33:48 PM UTC, original submission:
Switching between two branches with "monotone update -b newbranch" does not update to the head of the new branch and leaves the working directory in a weird state where a simple "monotone update" no longer takes you to the head of the current branch.
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 8 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-05-10 | stephen_leake | Open/Closed | In Test | Closed | |
2010-05-09 | stephen_leake | Status | None | Fixed | |
Open/Closed | Open | In Test | |||
2010-05-09 | stephen_leake | Status | Fixed | None | |
Open/Closed | In Test | Open | |||
2010-05-09 | stephen_leake | Status | None | Fixed | |
Open/Closed | Open | In Test | |||
2010-05-08 | stephen_leake | Assigned to | None | stephen_leake |
Powered by Savane 3.13-02a9.
Corresponding source code
I believe I had a mtn automate stdio session open on the same workspace, and I was using it in the middle of the command line sequence, and it was resetting _MTN/options (which is a related, but different, problem).
tests/update_-b_foo_updates__MTN_options_correctly confirms mtn is correct now.
So we can close this.