bzr revno always an integer, redux and new workflow questions
John Arbash Meinel
john at arbash-meinel.com
Wed Jan 9 08:53:26 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
On 2013-01-09 12:42, Chris Hecker wrote:
>> Pull and push are the only way to break the 'monotonically
>> increasing' behavior. So if you use "merge & commit" to update a
>> feature branch, it will always have proper increasing values.
> Hmm. Does this mean that if I use append_revisions_only=True on
> the feature branch I care about being monotonic, then I can skip
> all this rigamarole and just always merge from the server repo, and
> then push to it? Basically, aro=T would disable bzr pull, which is
> where my problem comes from anyway?
> Again, I only really care about a single feature branch being
> Would that simplify my workflow and be close to what I have now?
> I'd rather not have a bunch of branches around that I have to test
> and build, even with colo.
I'm not quite sure why that feature branch isn't actually your trunk.
But yes, it does sound like it would solve your situation.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Cygwin)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the bazaar