From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Johan Herland <johan@herland.net>
Cc: git@vger.kernel.org, Michael Poole <mdpoole@troilus.org>
Subject: Re: [RFC] git integrated bugtracking
Date: Sun, 03 Jun 2007 17:44:58 +0200 [thread overview]
Message-ID: <vpq1wgtnith.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20070603151921.GB30347@artemis> (Pierre Habouzit's message of "Sun\, 3 Jun 2007 17\:19\:21 +0200")
Pierre Habouzit <madcoder@debian.org> writes:
> Yeah, now that I read that thread, well yeah, I think notes are a hell
> of a good concept for my ideas. I mean, a bug report would be basically
> a collection of notes:
> * the bug has been found at this commit ;
> * the bug has been not-found at this commit ;
> * this commit is a fix for that bug ;
That's my feeling too. "Commiting" bug information in the tree is only
half of a good idea. You want to be able to say, after the fact, "This
commit had bug XYZ". OTOH, the idea (followed by bugs everywhere) that
merging a branch would automatically close bugs fixed by this branch
is a really cool thing.
The kind of information you're mentionning above can be a great
starting point for "bisect". I can even imagine a kind of distributed
bisect, where several users could give their "bad commits" for the
same bug.
--
Matthieu
next prev parent reply other threads:[~2007-06-03 15:45 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 [this message]
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
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=vpq1wgtnith.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=mdpoole@troilus.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).