Comment 4 for bug 731729
Revision history for this message
| John A Meinel (jameinel) wrote Re: [Bug 731729] Re: bzr should have one shelf per branch. | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 3/14/2011 1:01 PM, Stavros Korokithakis wrote:
> bzr-pipeline does what I describe, but I find the piping workflow not to
> be a good fit for what I'm doing. Basically, the colo plugin shelving
> all changes when switching branches would be *ideal*. That would enable
> me to just switch between feature branches at will, regardless of
> whether the feature is done or not. It would make my workflow *much*
> more efficient.
>
> Porting changes from other branches would be as simple as "bzr switch
> colo:other-branch --no-shelve" or something equivalent...
>
Out of curiosity, if you are using colo-branches for feature
development, why do you need to keep shelves around. why not just commit
the work and switch?
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAk1
FjEAoNd+
=LsDG
-----END PGP SIGNATURE-----