On Fri, Jun 10, 2011 at 01:31:54PM +1000, Ryan Mallon wrote:On 10/06/11 13:24, Joe Perches wrote:Not necessarily. You can leave the copyright bits intact but simplyOn Fri, 2011-06-10 at 13:13 +1000, Ryan Mallon wrote:If I strip my email address, but leave my name and copyright in theOn 10/06/11 13:11, Joe Perches wrote:I believe updating the MAINTAINERS file andOn Fri, 2011-06-10 at 13:05 +1000, Ryan Mallon wrote:Okay, what is the correct fix then so that people get the right emailOn 10/06/11 12:55, Paul Mundt wrote:get_maintainer uses the name and address in the first seenOn Fri, Jun 10, 2011 at 09:12:50AM +1000, Ryan Mallon wrote:I no longer work at Bluewater Systems. Update my email addressIs this sort of churn really necessary?
accordingly.
commit matching on the full name where possible.
address for me?
authoring and committing patches that take
your email address out of files works well.
files the patch will have the same amount of churn right?
update (or strip out) the address from the MODULE_AUTHOR part so people
still get the proper data from modinfo and so on. There are many people
with non-working email addresses in copyright statements tree-wide, so
there's certainly a precedent for it. It's also a motivator for not
bothering with inlining the email address in the future, unless it's to
avoid ambiguity (ie, a work done on behalf of an employer, who retains
all rights).
If there are files that you have authored but get_maintainers is
groveling the commits and using your old address, you can preempt this by
simply adding a MAINTAINERS entry with the appropriate file pattern, too.