On Tue, 2010-10-05 at 20:36 -0700, Stephen Boyd wrote:
I would not say it's common .. I don't recall seeing many other series
which do this. You shouldn't do it because the patch description doesn't
stand on it own. What if this patch is accepted in isolation, and the
others rejected would your description make sense? Also people don't
always look at a "series" in git history, sometimes you only look at one
commit so saying "next patch" or "this series" can be confusing.
You can have an intro email where you can describe the whole series,
including what your intending for each patch to do.
you might want to say what the purpose of the function is ..
I don't know, shouldn't hurt tho.
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora