[RFC] Revision id aliases

[Matthew D. Fuller]

On Tue, Jun 20, 2006 at 12:54:47PM -0400 I heard the voice of
Aaron Bentley, and lo! it spake thus:
> 
> I think you may be sitting in the wrong place.

Well, not wrong; just a different place from those for whom PQM is a
suitable answer   :]

Adding extra steps into the commit process wouldn't sit well with me,
and it certainly would be a non-starter with many of the people I'd
have to drag along to use bzr ("What, I have to commit, THEN run this
other command, THEN watch my email to see if it worked?  WTF?  Screw
this, I'm going back to having a thousand 'project.XXX' directories
instead of this VCS crap!").


I've got a workflow now that works.  I have my CVS checkout on any of
dozens of possible machines.  I make a change, I commit it, cvs goes
over ssh and talks to cvs on the server holding the repository, it
adds the change and sends an email.  I don't need to do anything on
the client side aside from HAVE CVS.  No SMTP config, no extra host
config, no plugins or CVS config, no nothing.  Aside from the "CVS"
bit, that's perfect.  All the brains are in one place, where they can
be controlled and maintained and setup and debugged once.

Considering the number of these machines covered in Python 2.3 stuff,
just getting bzr into play in the first place will be an ordeal that
may be insurmountable in places.  "Install bzr, then install this
plugin, then configure the mail daemon, then enable this plugin on
wherever you happen to have the branch, then access your email from
wherever you may be to see if commits work" is out of the question
totally.


-- 
Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.