Standing at the sink doing dishes, a bzr error message suddenly
flashed into consciousness::
bzr: ERROR: Working tree "C:/leo.repo/trunk/" has uncommitted
changes
Use --no-strict to force the push
I have just updated my bazaar.conf file so that "bzr push" gets
translated automatically to "bzr push --strict". This should be *all*
that is needed to ensure synchronization!!
This is the key that will unlock many good things.
===== Postmortem
Let me try to explain why I didn't see this answer that has been
staring me in the face for so long.
1. The problem arose initially ages ago, before bzr, before cvs.
Without bzr, the problem probably is intractable. I just didn't
notice the difference that bzr makes.
2. I was suffering massive confusion between *commits* and *pushes*.
"Unsynchronized" commits do not matter at all because the *local*
files are always in synch. The only thing that matters is that::
Pushes must push *all* changed files.
But that is exactly what bzr push --strict ensures.
===== Conclusions
1. I am in shock. This teensy-weensy insight allows me to consider
schemes that never seemed feasible before. Although bzr suffices,
this insight may allow me to confront using "fancier" sccs or db
approaches. Who knows where this may lead.
2. This is the "beautiful fact" that will rescue the "beautiful
theory" of tag files.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
