(Dropped some CC as this becomes a different topic) On Sat, Feb 8, 2014 at 2:20 AM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > Duy Nguyen wrote: > >> Don't take it the wrong way. I was just summarizing the last round. It >> surprised me though that this went under my radar. Perhaps a bug >> tracker is not a bad idea after all (if Jeff went missing, this bug >> could fall under the crack) > > I'm happy to plug > - http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=git;include=tags:upstream > - http://packages.qa.debian.org/common/index.html (email subscription link: > source package = git; under "Advanced" it's possible to subscribe to > bug-tracking system emails and skip e.g. the automated build stuff) > - https://www.debian.org/Bugs/Reporting (bug reporting interface - > unfortunately the important part is buried under "Sending the bug > report via e-mail") > again. :) So I wonder if we use debian bug tracker for git upstream. I haven't used debian tracker much (or debian for that matter). It's probably best just ask instead of searching and guessing. I suppose if debian people (mostly debian git maintainer?) are not opposed to us using their tracker for upstream bugs, then it's just a matter of associating a mail thread with a bug number for tracking. That could be probably be done via email, then reply all to the thread in question with a bug email address. After that all email discussions are also tracked via this bug email. Anybody can help track bugs. Say if 3 weekdays are over and nobody said a thing about something that looks a lot like bug, then it should be tracked (problems that can be quickly fixed do not need tracking). Hmm? -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html