Am Montag, den 17.09.2007, 18:58 +0200 schrieb Frank Lichtenheld: > On Mon, Sep 17, 2007 at 03:44:21PM +0200, Jelmer Vernooij wrote: > > * Package name : bundlebuggy > > Version : 0.0.1~bzr205 > > Upstream Author : Aaron Bentley <[EMAIL PROTECTED]> > > * URL : http://code.aaronbentley.com/bundlebuggy/ > > * License : GPLv2 or later > > Programming Lang: Python > > Description : Tool for tracking merge requests > > > > A tool that can recognize bzr merge requests posted to a mailing list and > > tracks votes for or against the merge requests on a mailing list or via a > > web > > interface. > If this only handles bzr merge requests it would probably be good to call > the binary package bzr-bundlebuggy or something like that, so that a user can > easily identify it as being closely related to bzr. For the source > package it probably doesn't matter much since the name isn't really > generic ;) Thanks, that's a good point.
From what I understand, it should be possible to add support for other version control systems. That's not likely to happen soon though, so I agree bzr-bundlebuggy would be the best name for now. Cheers, Jelmer -- Jelmer Vernooij <[EMAIL PROTECTED]> - http://samba.org/~jelmer/ Jabber: [EMAIL PROTECTED]
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
