Is it possible to switch and keep uncommitted changes?
Say I am working on some code, but I haven't gotten far enough to commit. Would it be possible for bzr-colo to save those changes in the respective branch when I switch? This would make my workflow many times easier and would increase my usage of branches tenfold. Right now, to branch, I also need to replicate databases, environments, certain misimported packages would fail, etc.
With colocated branches this is much easier, as I can create a new branch on-the-fly and come back to my original one for a quick fix, but right now I either have to commit my changes to the branch, shelve them (along with others I might have shelved) and reapply in the same order back, or live with them and cherry-pick files to commit.
Would it be possible for bzr-colo to save my changed files in a temporary directory and restore them when I switch back, or at the very least add per-branch shelving functionality (actually, is this possible now)?
Thanks.
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- bzr-colo Edit question
- Assignee:
- No assignee Edit question
- Last query:
- 2010-07-15
- Last reply:
- 2010-08-01
| Launchpad Janitor (janitor) said : | #1 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.
Can someone please answer this? This functionality is, for me, one of the most important features bzr could have.
| Launchpad Janitor (janitor) said : | #3 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.
