On Tue, Apr 26, 2011 at 8:18 PM, Felipe Contreras <felipe.contreras@xxxxxxxxx> wrote: > On Tue, Apr 26, 2011 at 3:09 PM, Stephen Kelly <steveire@xxxxxxxxx> wrote: >> Can git have a bug tracker please? > > So that you would feel comfortable that there would be a bug report > gathering dust? Or that it's closed as invalid for lack of > information? If you believe that it is a foregone conclusion that that is the fate of all bug trackers, and that that's a reasonable reason for git not to have one, then you have had very different experiences to me. I don't think there's more I can say than that. > >> This is another reminder to fix this bug which is otherwise untrackable. > > Let's imagine you are posting this to bugzilla: first question? > How do you reproduce this? My initial mail illustrated the problem as best I could: http://thread.gmane.org/gmane.comp.kde.devel.pim/29534 > > But I already asked you this[1], and you didn't reply. What should one > assume but that you don't care enough to help get this fixed. > > [1] http://article.gmane.org/gmane.comp.version-control.git/165320 Someone else replied. Isn't that enough? Other git developers confirmed it's probably an issue. Isn't that enough? http://thread.gmane.org/gmane.comp.kde.devel.pim/29534/focus=165326 Anyway, we've had a work around in place since January. From the git POV, this just falls through the cracks. Consider the bug marked as can not reproduce/needs info/whatever you prefer. I'm outie. Steve. -- 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