Re: [Monotone-devel] Re: rename boundary failure in 0.25

[Nathaniel Smith]

On Thu, Mar 09, 2006 at 03:04:54PM -0500, Shawn Samuel wrote:
> Thanks for the response, Nathaniel. I will just leave it alone until
> 0.26 is final, and then upgrade my team to it.

Makes sense.

> Some other stuff:
> 
> My team has been using monotone since last June and it's been
> terrific. We have a number of long-lived branches, and while we get
> the occasional spurious merge issue, overall it's been great. --lca
> was a huge time-saver in terms of reducing needless merge
> resolutions. I've used many source control systems (clearcase, svn,
> cvs, perforce, darcs, arch), and monotone does what I need better than
> anything I've ever used.

Wonderful!

0.26's merger should be as good or better than 0.25's default merger
at conservatively flagging conflicts, while better than 0.25 plus --lca
at cleanly merging clean stuff.  I apologize for you even needing to
use it!  Glad to hear it's been able to help you get stuff done,
though.

Perhaps you would like to update the wiki?:
  http://venge.net/monotone/wiki/Testimonials
  http://venge.net/monotone/wiki/ProjectsUsingMonotone
:-)

> We use (a slightly modified version of) the monotone buildbot to
> monitor each developer's "primary" branch, as well as our dev trunk -
> I got the mt buildbot code by downloading the tarball. Is it checked
> in anywhere, and what is the status of incorporating that stuff into
> buildbot proper? I had to upgrade the code to work against buildbot
> 0.70 to get some of the functionality I needed.

Oh, whoa, cool.  People actually want to use that? :-) Umm... yeah.  I
sent the patch in to Brian Warner (the buildbot guy) way back when I
first hacked it up, he didn't get around to integrating it, and I
haven't been bothering to follow up or even track buildbot releases --
one of those things where, hey, the server is still running, I'll
upgrade it any week now...

It needs some updates to work with 0.26 -- the code to parse revisions
to figure out what files were touched by a commit becomes incorrect.
(There's a stupid hack in the version running at http://venge.net:9000
right now to work around this, but a more proper solution is needed.)
Grahame Bowland might already written the needed code, for ViewMTN --
I'm not sure.  If so, we can just steal it...

If you're using it and have an updated patch, any chance you'd like to
drop a note to buildbot-devel?  Brian seemed quite interested in
getting the monotone support integrated when I met him at codecon, but
if nothing else then hearing that an end-user wants it too would
probably be good :-).  And I haven't had time to update the patch to
match upstream changes in buildbot.

> Also, as far as I can tell, there is no way to set the default key in
> monotonerc. Am I just missing something, or is there a reason for
> this?

Just the general reason that multi-key setups haven't seen as much use
as other things, so we haven't had as much feedback about what works
well or as much thought put into them.

-- Nathaniel

-- 
So let us espouse a less contested notion of truth and falsehood, even
if it is philosophically debatable (if we listen to philosophers, we
must debate everything, and there would be no end to the discussion).
  -- Serendipities, Umberto Eco