bzr shelve should have --keep
Bug #712449 reported by
Per Johansson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
High
|
Unassigned | ||
Breezy |
Triaged
|
Low
|
Unassigned |
Bug Description
One use case of the git staging area is where you stage your basic implementation of a feature, but then continue to work and try some changes that might or might not make it in. bzr could emulate this much better if bzr shelve has a keep option, eg:
<Work on basic implementation>
bzr shelve --all --keep
<Try an optimisation, which didn't work out>
bzr revert ; bzr unshelve
bzr ci -m "Feature A"
Since unshelve does have --keep, that can be used as a workaround, though it unnecessarily modifies the working tree.
tags: | added: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → High |
importance: | High → Low |
tags: | removed: check-for-breezy |
To post a comment you must log in.
Per Johansson пишет:
> Public bug reported:
>
> One use case of the git staging area is where you stage your basic
> implementation of a feature, but then continue to work and try some
> changes that might or might not make it in. bzr could emulate this much
> better if bzr shelve has a keep option, eg:
>
> <Work on basic implementation>
> bzr shelve --all --keep
> <Try an optimisation, which didn't work out>
> bzr revert ; bzr unshelve
> bzr ci -m "Feature A"
>
> Since unshelve does have --keep, that can be used as a workaround,
> though it unnecessarily modifies the working tree.
I agree. So, there is workaround already, but it will be nice to have
such feature.