[Erc-help] Re: Should we move to savannah.gnu.org?

[Michael O. <mw...@gn...>]

Damien Elmes <erc...@re...> writes:

> Have you tried bazaar-ng? The current implementation's in python
> which I'm sure will bother some people, and it's still quite new in
> parts, but it seems to be quite nicely designed. The design is
> closer to darcs or bitkeeper than the original arch.

I'm trying it out on a few small school-related projects.  It seems to
do the basics reasonably well.  It doesn't handle the concept of
"pushing" changes very well, though -- I have to run the revert
command to update my reference copy when I push changes from a remote
machine.

I guess I'll go into a few of the reasons that I like Arch so well.

1. Repository and project namespace.  From the name of a repository
   you can glean an email address and a rough estimate of how old the
   projects contained in it are.  From the project triple, you get the
   name of the project, an identifying tag, and a version number.  It
   seems like a very elegant way to identify a branch: one that makes
   it easy to write archive-browsing interfaces.

2. Automatic generation of ChangeLog entries is at least somewhat
   feasible by means of using a consistent layout in your commit
   messages.  This doesn't have much practical use for ERC,
   admittedly, since it must now use Emacs-style ChangeLog files.

I try to be flexible when it comes to revision control systems.  As
long as the revision control system that we use doesn't have esoteric
command line options (-z3 ... ugh), non-atomic commits, and clumsy
methods of handling file renames and deletions, like CVS, I'll be
content with it.

=2D-=20
Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/
Interests: Emacs Lisp, text markup, protocols -- Muse, Planner, ERC, EMMS
  /` |\ | | | IRC: mwolson on freenode.net: #hcoop, #muse, #PurdueLUG
 |_] | \| |_| Jabber: mwolson_at_hcoop.net