git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: Petr Baudis <pasky@suse.cz>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Git Survey summary
Date: Thu, 21 Sep 2006 12:48:18 -0400	[thread overview]
Message-ID: <20060921164818.GF3934@spearce.org> (raw)
In-Reply-To: <20060921163732.GX8259@pasky.or.cz>

Petr Baudis <pasky@suse.cz> wrote:
> Dear diary, on Thu, Sep 21, 2006 at 05:56:17PM CEST, I got a letter
> where Shawn Pearce <spearce@spearce.org> said that...
> > I'm all for hyperlink integration of gitweb and bug tracking systems
> 
> Actually, Trac might be interesting if you want tight VCS web interface
> and bugtracking web interface integration, although Trac is not very
> powerful. I think the OLPC people did some work on integrating Trac and
> Git.
> 
> People will think I'm weird, but I have to admit that I rather do like
> Bugzilla.

Your not weird.  I also like Bugzilla for some projects; its rather
simple and somewhat easy to use...  I also know a lot of people
who hate it.

> I think we are doing fine as it is for now, though.

Oh I agree completely.  But that's the Git project.

However I think it would be nice if we had native hooks shipped
with core Git to connect to some popular bug tracking systems such
as Bugzilla and Trac.  Nothing incredibly fancy, but like how we
currently ship some default example hooks (and even install them into
every repo with `git init-db`!) we should at least ship some basic
examples and documentation for integrating to some popular systems.
Integrate with at least 2 and it should be easy for users to add
others...

Eh, its just more stuff for an ever growing wishlist.  :-)
I probably won't do it as its not high on my wish list for Git.
I don't currently use any bug tracking systems.

-- 
Shawn.

  reply	other threads:[~2006-09-21 16:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12  9:05 Git Survey summary Nguyễn Thái Ngọc Duy
2006-09-21 14:12 ` Nguyễn Thái Ngọc Duy
2006-09-21 15:23   ` Jakub Narebski
2006-09-21 15:56     ` Shawn Pearce
2006-09-21 16:13       ` Jakub Narebski
2006-09-21 16:27         ` Shawn Pearce
2006-09-21 16:34           ` Petr Baudis
2006-09-21 16:49             ` Jakub Narebski
2006-09-21 16:44           ` Jakub Narebski
2006-09-21 16:37       ` Petr Baudis
2006-09-21 16:48         ` Shawn Pearce [this message]
2006-09-21 16:49     ` Nguyen Thai Ngoc Duy
2006-09-21 17:00       ` Petr Baudis

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=20060921164818.GF3934@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=pasky@suse.cz \
    /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 NNTP newsgroup(s).