From: Jakub Narebski <jnareb@gmail.com>
To: Pierre Habouzit <madcoder@debian.org>
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>,
Thomas Harning <harningt@gmail.com>,
git@vger.kernel.org
Subject: Re: [RFC] Idea for Git Bugtracking Tool
Date: Sat, 8 Mar 2008 15:23:13 +0100 [thread overview]
Message-ID: <200803081523.14340.jnareb@gmail.com> (raw)
In-Reply-To: <20080308134210.GA3230@artemis.madism.org>
Dnia sobota 8. marca 2008 14:42, Pierre Habouzit napisał:
> On Fri, Mar 07, 2008 at 11:10:18PM +0000, Jakub Narebski wrote:
>> Matthieu Moy <Matthieu.Moy@imag.fr> writes:
>>
>>> Thomas Harning <harningt@gmail.com> writes:
>>>
>>>> Any ideas/flaws with this concept? Anybody up for taking on this
>>>> project... or for taking this up as a GSOC project mentor?
>>>
>>> Already discussed here:
>>>
>>> http://thread.gmane.org/gmane.comp.version-control.git/48981/
>>>
>>> Pierre Habouzit started working on something called grit, which
>>> seems to be dead.
>>
>> Pierre, what happened to git://git.madism.org/grit.git ?
>
> it was very badly coded, and not going in the proper direction.
Should it be then removed from InterfacesFrontendsAndTools wiki page
(perhaps putting "Bugs Everywhere", with Git as one of supported version
control backends in its place)?
> We discussed design with Dscho a couple of time, I know how to build
> such a tool in git (at least a bit how) but I never found the time.
Care to share those thoughts, and what mistakes were made?
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-03-08 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 19:22 [RFC] Idea for Git Bugtracking Tool Thomas Harning
2008-03-06 20:08 ` Matthieu Moy
2008-03-07 23:10 ` Jakub Narebski
2008-03-08 13:42 ` Pierre Habouzit
2008-03-08 14:23 ` Jakub Narebski [this message]
2008-03-08 15:02 ` Pierre Habouzit
2008-03-09 8:26 ` Jan Hudec
2008-03-11 3:29 ` Thomas Harning
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=200803081523.14340.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=harningt@gmail.com \
--cc=madcoder@debian.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).