From: Pierre Habouzit <madcoder@debian.org>
To: Yann Dirson <ydirson@altern.org>
Cc: "Johan Herland" <johan@herland.net>,
git@vger.kernel.org, "Michael Poole" <mdpoole@troilus.org>,
"Karl Hasselström" <kha@treskal.com>,
"Catalin Marinas" <catalin.marinas@gmail.com>
Subject: Re: [RFC] git integrated bugtracking
Date: Sun, 3 Jun 2007 22:21:17 +0200 [thread overview]
Message-ID: <20070603202117.GG30347@artemis> (raw)
In-Reply-To: <20070603200431.GF6992@nan92-1-81-57-214-146.fbx.proxad.net>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On Sun, Jun 03, 2007 at 10:04:31PM +0200, Yann Dirson wrote:
> One thing that I just thought about is how such a system would play
> with eg. StGIT.
I read the rest of the mail, but I don't know stgit at all, so I'm not
really able to tell how well it would integrate, especially since well,
it's still early.
But for sure, I'm launching that brainstorming thread because I want
as much input as possible to know what are people needs, and add the one
that make sense to the todo list, the one that would be good to the
wishlist. FWIW playing well with usual git tools (like stgit, guilt, and
whatever other evolved "thing" in the git nebula) is definitely in the
TODO list.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-03 20:21 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 11:48 [RFC] git integrated bugtracking Pierre Habouzit
2007-06-03 12:35 ` Yann Dirson
2007-06-03 13:23 ` Pierre Habouzit
2007-06-03 12:59 ` Michael Poole
2007-06-03 13:31 ` Pierre Habouzit
2007-06-03 13:48 ` Johan Herland
2007-06-03 15:19 ` Pierre Habouzit
2007-06-03 15:44 ` Matthieu Moy
2007-06-03 16:07 ` Pierre Habouzit
2007-06-03 17:35 ` david
2007-06-03 18:49 ` Pierre Habouzit
2007-06-03 19:07 ` david
2007-06-03 20:31 ` Yann Dirson
2007-06-03 17:10 ` Yann Dirson
2007-06-03 20:04 ` Yann Dirson
2007-06-03 20:21 ` Pierre Habouzit [this message]
2007-06-04 22:03 ` Yann Dirson
2007-06-04 22:25 ` Pierre Habouzit
2007-06-03 19:22 ` Linus Torvalds
2007-06-03 20:16 ` Pierre Habouzit
2007-06-03 23:07 ` Martin Waitz
2007-06-04 9:32 ` Rogan Dawes
[not found] ` <20070604102037.GB7758@.intersec.eu>
2007-06-04 13:29 ` Rogan Dawes
2007-06-03 20:17 ` Yann Dirson
2007-06-03 20:32 ` Pierre Habouzit
2007-06-09 12:12 ` Pierre Habouzit
2007-06-09 16:23 ` Jakub Narebski
2007-06-10 2:44 ` Daniel Barkalow
2007-06-10 7:44 ` Johannes Schindelin
2007-06-10 6:59 ` Martin Langhoff
2007-06-10 7:35 ` Junio C Hamano
2007-06-10 8:38 ` Martin Langhoff
2007-06-10 8:50 ` Jan Hudec
2007-06-11 18:51 ` Jon Loeliger
2007-06-12 8:54 ` Guilhem Bonnefille
2007-06-10 8:37 ` Jan Hudec
2007-06-10 8:55 ` Martin Langhoff
2007-06-10 10:16 ` Pierre Habouzit
2007-06-10 23:14 ` Martin Langhoff
2007-06-11 8:45 ` Pierre Habouzit
2007-06-11 10:00 ` Martin Langhoff
2007-06-10 10:49 ` Jan Hudec
2007-06-10 22:07 ` Matthieu Moy
2007-06-10 13:34 ` Pierre Habouzit
2007-06-10 13:43 ` Pierre Habouzit
2007-06-10 14:02 ` Pierre Habouzit
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=20070603202117.GG30347@artemis \
--to=madcoder@debian.org \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=kha@treskal.com \
--cc=mdpoole@troilus.org \
--cc=ydirson@altern.org \
/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).