git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git maintenance bug tracker sooner better than later

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 3, 2009, 14:42 UTC
Message-ID
<alpine.DEB.1.00.0902031541100.6573@intel-tinevez-2-302>
In-Reply-To
<87ab93fxod.fsf@iki.fi>
Hi,
On Tue, 3 Feb 2009, Teemu Likonen wrote:
Show 16 quoted lines
> On 2009-02-03 19:05 (+0900), Nanako Shiraishi wrote:
> 
> > Quoting jidanni@jidanni.org:
> >
> >> I predict that git maintenance will have to adopt a bug tracker. Just
> >> like many other packages that relied on just sending bugs and patches
> >> to a mailing list, in the end ended up adding a bug tracker.
> >
> > Thanks for sharing your insight.
> >
> > A more important thing is what you are going to do about it.
> 
> Maybe he would file a lot of bug reports. At least in Debian there are
> about 1800 reports from jidanni@jidanni.org:
> 
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?submitter=jidanni@jidanni.org
Definitely too much time on his hands.

If I had that much time, I know exactly what projects I would tackle: there are good ideas on the GSoC page, and it is highly unlikely all of them will be taken/sponsored by GSoC.

Ciao, Dscho

Previous: Teemu LikonenNext: jidanni@jidanni.org
Message 5 of 10 in “git maintenance bug tracker sooner better than later”
  1. jidanni@jidanni.orgFeb 2, 2009
  2. Christian MICHONFeb 2, 2009
  3. Nanako ShiraishiFeb 3, 2009
  4. Teemu LikonenFeb 3, 2009
  5. Johannes SchindelinFeb 3, 2009
  6. jidanni@jidanni.orgFeb 4, 2009
  7. Johannes GilgerFeb 6, 2009
  8. Andreas EricssonFeb 6, 2009
  9. jidanni@jidanni.orgFeb 6, 2009
  10. Johannes GilgerFeb 6, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.