Markus Heidelberg <markus.heidelberg@xxxxxx> writes: > It is already in next, I think a following patch should be against next > now, shouldn't it? Surely, and thanks. If you look at the output of $ git log --first-parent origin/master..origin/next You will find the tip of mh/maint-sendmail-cc-doc topic branch is at bd7c6e7 (doc/git-send-email: mention sendemail.cc config variable, 2008-12-29). I'll apply any follow-up patch to the topic on top of that commit, and then merge the result to 'next' (and 'master'/'maint' when the result is ready). In rare cases when there are other topics in 'next' that touch vicinity of the code you are modifying, a patch made against 'next' may not apply cleanly to the topic, but I'll wiggle it to apply anyway (that is what the maintainers do), so it would certainly be nicer if you sent a patch to the tip of the topic you are updating, but there is no need to worry about such conflicts too much. -- 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
