On Fri 23 Nov 2007 at 02:35:17 -0600, Matthew D. Fuller wrote: > Yes, the entire run from a97d0dcc up through 4da549 happened in my > private branch. While mtn isn't the way I went for my own stuff, > working with a DVCS has well trained me to make throwaway branches for > anything that looks likely to take more than 1 commit to do. > > I'm not sure what viz is showing breakage for, though; eyeballing the > ancestry, it's unbroken, and I thought propagate would add on the > X.ctwm branch certs. This is the boundaries of my mtn understanding, > though.
Yes, I'd assume it would appear unbroken to you, since you made the commits into your repository. However in mine, the two are not connected: the older one (a97d0dcc) is the end of the line and the newer one (4da549) is the beginning of a new line. Fortunately it is shown just like when you choose to view only a subset of all revisions. The difference is that there is no way to make them visible since they are not present in my repository. I made a screenshot here: http://www.falu.nl/~rhialto/monotone.png So, given the workflow that you describe, it sounds like monotone should be made to add a sort of short-cut connection between the two unconnected revisions. -Olaf. -- ___ Olaf 'Rhialto' Seibert -- You author it, and I'll reader it. \X/ rhialto/at/xs4all.nl -- Cetero censeo "authored" delendum esse.
