From: Christian MICHON <christian.michon@gmail.com>
To: jidanni@jidanni.org
Cc: git@vger.kernel.org
Subject: Re: git maintenance bug tracker sooner better than later
Date: Mon, 2 Feb 2009 23:07:38 +0100 [thread overview]
Message-ID: <46d6db660902021407x3e2a1531mb2189d9f4a3b55b3@mail.gmail.com> (raw)
In-Reply-To: <87myd4fyip.fsf@jidanni.org>
On Mon, Feb 2, 2009 at 8:07 PM, <jidanni@jidanni.org> wrote:
> I predict that git maintenance will have to adopt a bug tracker.
>
will it snow tomorrow ? ;-)
--
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
next prev parent reply other threads:[~2009-02-02 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 19:07 git maintenance bug tracker sooner better than later jidanni
2009-02-02 22:07 ` Christian MICHON [this message]
2009-02-03 10:05 ` Nanako Shiraishi
2009-02-03 13:38 ` Teemu Likonen
2009-02-03 14:42 ` Johannes Schindelin
2009-02-04 0:28 ` jidanni
2009-02-06 12:33 ` Johannes Gilger
2009-02-06 12:56 ` Andreas Ericsson
2009-02-06 13:24 ` jidanni
2009-02-06 16:30 ` Johannes Gilger
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=46d6db660902021407x3e2a1531mb2189d9f4a3b55b3@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=git@vger.kernel.org \
--cc=jidanni@jidanni.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).