On Thu, Apr 05, 2012 at 06:20:53PM -0700, Junio C Hamano wrote: > >> > CC: Jeff King <peff@xxxxxxxx> > >> > CC: Phil Hord <phil.hord@xxxxxxxxx> > >> > CC: Junio C Hamano <gitster@xxxxxxxxx> > >> > --- > >> > >> Please don't do "Cc:" here; they belong to your e-mail header. > >> > > You mean place them below the snip line? I can do that. > > No. When you review and fix typo in format-patch output, you can add > these to the e-mail header part and git-send-email will pick them up just > fine. I think there is a legitimate conflict of interest here. It's not clear exactly what "cc" tags in a commit message mean, because it is really a per-project thing. I don't work on the kernel, but I always took their cc tag to mean "these are people interested in this topic area". Send-email helpfully picks up that hint and cc's them on the emailed patch. And when the patch is applied, those cc lines remain, because people reading "git log" much later may find a bug in the patch, and it is helpful to tell them the people interested in the area. In git.git, though, we don't typically use such cc tags. Perhaps because we are a much smaller project than the kernel, or perhaps for other logistical reasons. And even if we did, the cc list above does not really meet the guideline I gave. They are people who happened to review your patch or comment on the list, not people who are interested forever in a particular subsystem. So from the maintainer's and the project's perspective, those cc lines are useless noise. But from the submitter's point of view, it may be convenient to tell git "these are people who have reviewed _this_ patch series", and have it automatically cc them on each iteration of the series without re-typing their addresses. And because of the send-email behavior I mentioned above, the "cc" tags are a convenient place to put it. So it is a piece of information that is useful to the submitter, but not to the maintainer. Where can the submitter put it that will help themselves, but not bother the maintainer? I wonder if the right solution would be an option for send-email to respect cc lines, but strip them out of the body of the sent patch. -Peff -- 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