> You also told us that git commits and >> trac tickets are orthogonal, and there is no such thing as a "ticket to >> which this commit belongs". > > > Still off topic, but that is just how things are. > > I would gently argue that this is an interpretation of how our workflow works, and that a new observer would perhaps be surprised to learn that the sometimes voluminous discussion on Trac tickets leading to very precise commits means there is no such thing. Just because Git doesn't know (and I think it does, because of your merge commits) doesn't mean there isn't a connection.
> > >> Now you tell us that we should look up the >> email addresses of ticket participants and contact them directly, rather >> than simply using trac to send a question to the participants. > > > I haven't said that. You should also consider opening a thread on > sage-devel or ask.sagemath besides emailing the author (who you can > trivially look up with git blame). Just because somebody was cc'd on some > old ticket doesn't mean that he still remembers what went down, or is the > one who is currently working on that part of Sage. > I have to agree with several others that this is poppycock. Not being able to comment on a closed ticket essentially dooms a new discussion to obscurity - sage-devel because it's too general, a new ticket is too hard to find. I do agree that there shouldn't be prolonged discussions on closed tickets, but a ping "Hey, there's this new ticket, or this question on ask.sagemath which is relevant" often has been very helpful to me, both when cc:ed on a ticket and when asking a question. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
