Jeff King <peff@xxxxxxxx> writes: > There was some discussion about this a while back for the kernel. Some > relevant points that I recall: > > - there's more than _one_ maintainer for the repo; in fact, who you > email depends on what part of the code you are touching > > - this information could be shipped as part of the repo (i.e., under > version control like the rest of the project, as it changes with the > project) > > - this information can potentially be inferred from git shortlog > and/or blame; this addresses the problem of data becoming stale > > See this thread: > > 1187110824.32555.76.camel@localhost">http://mid.gmane.org/1187110824.32555.76.camel@localhost That matches my recollection, but I think the most important point to take home from these points are that you cannot blindly say that the tool can figure it out and do that for you. We could probably have an automated way to scan shortlog and whatnot and offer suggestions, but the final determination of the recipient addresses needs to be done by the end user. Which in short means README or Documentation/SubmittingPatches would be the most appropriate place for that information. - 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
