Fossil SCM
"fossil update" should get current branch if multiple descendants
Fixed
33d2bf39889352f…
· opened 15 years, 3 months ago
- Type
- Feature_Request
- Priority
- —
- Severity
- Minor
- Resolution
- Fixed
- Subsystem
- —
- Created
- Dec. 13, 2010 5:07 p.m.
This is something which has bothered me for a while:
"A", "B" and "C" check out a repo. "B" and "C" make changes. "B" checks in on a new branch, "C" checks in on the original branch. Now, when "A" does fossil update, he gets a nice informational message about the two descendant branches, but fossil does not get anything unless told which branch to get.
My suggestion is that fossil update should always get the branch it was on originally unless told otherwise. It should also inform the user if there are new branches in the meantime, but the existence of new branches should be informative and not an obstacle.