Stefan Beller <sbeller@xxxxxxxxxx> writes: > On Wed, Mar 16, 2016 at 3:51 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > >> A few "characteristics" of that list, that cannot be updated by >> anybody but me (because it is just my personal collection after all) >> are: >> >> * I do not have to worry about useless new entries that do not >> align the overall system design getting added by clueless people. > > As it is your personall collection and you're the maintainer, I thought > of this as a collection with maintainers blessing, i.e. if the code&tests > are not too shoddy a patch will get accepted (read as: On that list there > are no bullet points with fundamental design issues). Why would you > add things to that list if you'd not agree with them? If it was not clear, I didn't mean these three are all bad things. In fact, this first of the three "characteristics" is a good thing. Random people are not allowed to throw random things into it. >> * Adding new entry after scanning past list traffic and finding a >> still unresolved topic that "died down" is relatively easy. > > As the notes in Documentation/howto/maintain-git.txt indicate, you're > scanning the list anyway, so offering help in this point may be moot. The scanning of the list for new topics (to further discuss and pick patches to queue) and the scanning of the list for "died down" threads are two completely separate activities. If somebody with good taste can do the latter when I am too busy elsewhere by pointing out "what happened to this thread? It seems that nobody is interested enough to pursue it right now, so perhaps it is a good time to add it to 'leftover bits' list?", that would be helpful. And as you agreed, pointing out "done" items to remove would also be helpful. Thanks. -- 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