Re: [PG-devel] ChangeLog branch chaos

2011-04-28 Thread Makarius
On Thu, 28 Apr 2011, David Aspinall wrote: I am keen to use a more modern distributed system but it probably means choosing an external provider rather than trying to get the University to provide yet another semi-supported tool that works at the beginning and then rusts. Sourceforge is the

Re: [PG-devel] ChangeLog branch chaos

2011-04-28 Thread David Aspinall
I'd recommend Savannah (either as a GNU or a non-GNU project). interesting idea, good choice of VC systems there, not just bzr Which reminds me: it would be nice to include PG into the GNU ELPA (a package archive from which Elisp packages can be installed conveniently via package.el). If

Re: [PG-devel] ChangeLog branch chaos

2011-04-28 Thread David Aspinall
I would not expect a paragraph that starts with modern end with Sourceforge. They added some half-harted support for Mercurial, Bazaar, Git some years ago, and people rightly complained that it was too late and too little. There are several reasons to suggest sf. One is the provision of

Re: [PG-devel] ChangeLog branch chaos

2011-04-28 Thread Makarius
On Thu, 28 Apr 2011, David Aspinall wrote: There are several reasons to suggest sf. One is the provision of trac. So you actually like trac? As a German I always pronounce it with a very soft t. Seriously: I am looking for a really good issue tracker for a few years already, one that

Re: [PG-devel] ChangeLog branch chaos

2011-04-27 Thread Stefan Monnier
default. There is no real fix, because cvs log cannot generate all information that belongs to a particular branch. Even Debian Actually, there is a real fix: convert the CVS repository to some other (saner?) format like Bazaar or Git, and then use those tools to get the change log for