`amp update` fails to switch between two branches
Reported by seydar | June 30th, 2010 @ 07:09 PM
amp update fails to switch between two
branches.
[ari: ~/src] amp init test New hg repository initialized.
[ari: ~/src] cd test/ [ari: ~/src/test] amp add Ampfile File
Ampfile has been added at Wed Jun 30 15:07:30 -0400 2010
[ari: ~/src/test] amp commit -m 'adsf' status: opening journal
status: Ampfile
status: closing journal
[ari: ~/src/test] amp branches scanning
default 0:c6ab6b3e0e
[ari: ~/src/test] amp branch new_branch status: marked working
directory as branch new_branch
[ari: ~/src/test] amp commit -m 'new branch' status: opening
journal
status: closing journal
[ari: ~/src/test] amp branch new_branch
[ari: ~/src/test] amp update -C default scanning
status: resolving manifests
status: 0 files unresolved, 0 files merged, 0 files removed, 0
files updated
[ari: ~/src/test] amp branch new_branch
[ari: ~/src/test] hg branch new_branch
[ari: ~/src/test]
it was supposed to say 'default' after amp branch,
instead of 'new_branch'
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Rethink Version Control.- http://amp.carboni.ca/
Amp aims to put control of version-control software in your hands as a developer. The entire system is written in Ruby (with C extensions to improve performance), and aims to implement all major VCS's in Ruby. Currently, Mercurial is implemented.
Other features:
Commands are first-class members of the system - drop in an "Ampfile" in your repository, and you can add commands to amp in the same manner you add commands to rake (only with far, far more power!)
Documentation is one of our biggest priorities. We require all methods to be documented - even comically simple ones.
Heavy testing.
Multiple "workflows" - use git's commands to power a mercurial repository.
Add hooks/callbacks in minutes.
seydar