public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Kristis Makris <kristis.makris@asu.edu>
To: developers@bugzilla.org, help-gnats@gnu.org,
	dev@subversion.tigris.org, dev@ccvs.cvshome.org
Cc: tonyg@kcbbs.gen.nz, steve@einval.com
Subject: Scmbug
Date: Tue, 01 Jun 2004 12:39:00 -0000	[thread overview]
Message-ID: <1085962119.1380.0.camel@syd.mkgnu.net> (raw)

Greetings.

I'd like to announce Scmbug, a tool providing integration of Source code
Configuration Management with Bugtracking. It is meant to be a universal
tool that can glue any source code version control system with any
bugtracking tool, for all platforms.

In the current development release, Scmbug supports integrating CVS with
Bugzilla. The intention is to integrate other source code version
control tools (e.g. Subversion) with other bugtracking systems (e.g.
gnats) in a consistent and more flexible manner other independent tools
currently do so (e.g. Tony Garnock-Jones' cvszilla from
http://homepages.kcbbs.gen.nz/~tonyg/, Steve McIntyre's integration from
http://www.einval.com/~steve/software/cvs-bugzilla/ ).

I would encourage developers and users of integration glue to contribute
to this general integration tool, rather than continue the fragmentation
of individual tools attempting to resolve the same problem.

The latest development release is available at:
http://www.public.asu.edu/~makrists/scmbug/

Regards,
Kristis Makris



_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

                 reply	other threads:[~2004-05-31  0:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1085962119.1380.0.camel@syd.mkgnu.net \
    --to=kristis.makris@asu.edu \
    --cc=dev@ccvs.cvshome.org \
    --cc=dev@subversion.tigris.org \
    --cc=developers@bugzilla.org \
    --cc=help-gnats@gnu.org \
    --cc=steve@einval.com \
    --cc=tonyg@kcbbs.gen.nz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).