On Mon, Sep 20, 2010 at 01:46, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Ãvar ArnfjÃrà Bjarmason <avarab@xxxxxxxxx> writes: > >> Is there a reason for why this didn't get picked up other than falling >> through the cracks? > > Simply because I wasn't actively collecting new topics during feature > freeze, especially for small stuff that I knew that resending after > release would be trivial and more efficient use of my time than queuing it > in 'pu' and having to look at it every time I do another push-out in order > to decide when to merge it to 'next'. Rigth, I have no problem doing $whatever to get patches in, but the problem I often have is that I don't know what state things are in, and what I'm supposed to do at any given time. E.g. in this case I submitted the "send-email: use catfile() to concatenate files" patch 2 days after this one, that one got into the next "What's cooking in git.git" post. Since both were trivial fixes and there was no comment on this one I was inclined to think that it just fell through. Should I generally re-send patches that I've sent, haven't had comments, and haven't appeared in subsequent "What's cooking in git.git" posts (given that some reasonable amount of time has passed since the original send) ? Then there's stuff like my "git-am: Ignore whitespace before patches" which had some comments, but which *I* still think is OK as-is. Should I just keep pushing stuff like that until someone tells me to stop? Thanks, from a list member somewhat confused about the patch queue :) -- 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