Skip to contentSkip to conversation

MAINTAINERS: Replace my amsat.org email address

PATCH Applied Philippe Mathieu-Daudé 8 participants 9 messages Oct 17, 2022 – May 25

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 MAINTAINERS: Replace my amsat.org email address

The amsat.org domain is having issues with DMARC / SPF / DKIM:
https://lore.kernel.org/qemu-devel/CAMVc7JUy5NeEN0q=4zfZvn_rppgqn9wicV1z=TsLuHKS3RY3Sw@mail.gmail.com/

Consolidate all of my MAINTAINERS entries on my work address.

---
 .mailmap    |  4 +++-
 MAINTAINERS | 62 ++++++++++++++++++++++++++---------------------------
 2 files changed, 34 insertions(+), 32 deletions(-)
.mailmap +3 -1
index 1f7319b70b..35dddbe27b 100644
@@ -70,7 +70,9 @@ Paul Burton <[email protected]> <[email protected]>
 Paul Burton <[email protected]> <[email protected]>
 Paul Burton <[email protected]> <[email protected]>
 Paul Burton <[email protected]> <[email protected]>
-Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
 Stefan Brankovic <[email protected]> <[email protected]>
 Yongbok Kim <[email protected]> <[email protected]>
 
MAINTAINERS +31 -31

246 lines not on this page · raw message

Signature · 1 line
2.37.3
#1 lore raw
Quoted 11 lines · Philippe Mathieu-Daudé

The amsat.org domain is having issues with DMARC / SPF / DKIM:
https://lore.kernel.org/qemu-devel/CAMVc7JUy5NeEN0q=4zfZvn_rppgqn9wicV1z=TsLuHKS3RY3Sw@mail.gmail.com/

Consolidate all of my MAINTAINERS entries on my work address.

---
 .mailmap    |  4 +++-
 MAINTAINERS | 62 ++++++++++++++++++++++++++---------------------------
 2 files changed, 34 insertions(+), 32 deletions(-)

Thanks, applied to qemu.git/master.

Stefan

#2 lore raw
In reply to Philippe Mathieu-Daudé
Quoted 3 lines · Philippe Mathieu-Daudé

The amsat.org domain is having issues with DMARC / SPF / DKIM:
https://lore.kernel.org/qemu-devel/CAMVc7JUy5NeEN0q=4zfZvn_rppgqn9wicV1z=TsLuHKS3RY3Sw@mail.gmail.com/

Yeah, I noticed this before, and gmail marks the email as spam, and patchwork simply drops the patch email silently ...

Quoted 9 lines

Consolidate all of my MAINTAINERS entries on my work address.

---
 .mailmap    |  4 +++-
 MAINTAINERS | 62 ++++++++++++++++++++++++++---------------------------
 2 files changed, 34 insertions(+), 32 deletions(-)

Regards,
Bin

#3 lore raw
In reply to Philippe Mathieu-Daudé
Quoted 16 lines · Philippe Mathieu-Daudé

The amsat.org domain is having issues with DMARC / SPF / DKIM:
https://lore.kernel.org/qemu-devel/CAMVc7JUy5NeEN0q=4zfZvn_rppgqn9wicV1z=TsLuHKS3RY3Sw@mail.gmail.com/

Consolidate all of my MAINTAINERS entries on my work address.

---
 .mailmap    |  4 +++-
 MAINTAINERS | 62 ++++++++++++++++++++++++++---------------------------
 2 files changed, 34 insertions(+), 32 deletions(-)
.mailmap +0 -0
index 1f7319b70b..35dddbe27b 100644

.mailmap Paul Burton <[email protected]> <[email protected]> · line 74

Quoted 6 lines
.mailmap +2 -1
@@ -70,7 +70,9 @@ Paul Burton <[email protected]> <[email protected]>
 Paul Burton <[email protected]> <[email protected]>
 Paul Burton <[email protected]> <[email protected]>
 Paul Burton <[email protected]> <[email protected]>
-Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>

I think this retroactively credits all your contributions to Linaro. Intentional?

Quoted 4 lines
.mailmap +1 -0
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
 Stefan Brankovic <[email protected]> <[email protected]>
 Yongbok Kim <[email protected]> <[email protected]>
 

[...]

#4 lore raw
Quoted 13 lines · Markus Armbruster
Quoted 11 lines · Philippe Mathieu-Daudé

The amsat.org domain is having issues with DMARC / SPF / DKIM:
https://lore.kernel.org/qemu-devel/CAMVc7JUy5NeEN0q=4zfZvn_rppgqn9wicV1z=TsLuHKS3RY3Sw@mail.gmail.com/

Consolidate all of my MAINTAINERS entries on my work address.

---
  .mailmap    |  4 +++-
  MAINTAINERS | 62 ++++++++++++++++++++++++++---------------------------
  2 files changed, 34 insertions(+), 32 deletions(-)
Quoted 14 lines

.mailmap Paul Burton <[email protected]> <[email protected]> · line 74

Quoted 11 lines
.mailmap +2 -1
index 1f7319b70b..35dddbe27b 100644
@@ -70,7 +70,9 @@ Paul Burton <[email protected]> <[email protected]>
  Paul Burton <[email protected]> <[email protected]>
  Paul Burton <[email protected]> <[email protected]>
  Paul Burton <[email protected]> <[email protected]>
-Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>

I think this retroactively credits all your contributions to Linaro. Intentional?

Certainly not intentional. I was seeing this as a git limitation, but Alex pointed to me we are doing an invalid use of git-mailmap, since it is described as:

... the file .mailmap [...] is used to map author and committer names and email addresses to canonical real names and email addresses.

so more for typos, not developers changing email addresses. So our "replace old addresses by a more recent one" section might not be the best use. I think it was useful for the get_maintainer.pl fallback
option: when a file is not cover in MAINTAINERS then the script look at git history. If all files are well covered, then we shouldn't need this fallback anymore, nor this .mailmap translation.

Quoted 8 lines
Quoted 5 lines
.mailmap +1 -0
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
  Stefan Brankovic <[email protected]> <[email protected]>
  Yongbok Kim <[email protected]> <[email protected]>
 

[...]

#5 lore raw
Quoted 37 lines · Philippe Mathieu-Daudé
Quoted 13 lines · Markus Armbruster
Quoted 11 lines · Philippe Mathieu-Daudé

The amsat.org domain is having issues with DMARC / SPF / DKIM:
https://lore.kernel.org/qemu-devel/ CAMVc7JUy5NeEN0q=4zfZvn_rppgqn9wicV1z=TsLuHKS3RY3Sw@mail.gmail.com/

Consolidate all of my MAINTAINERS entries on my work address.

---
  .mailmap    |  4 +++-
  MAINTAINERS | 62 ++++++++++++++++++++++++++---------------------------

  2 files changed, 34 insertions(+), 32 deletions(-)
Quoted 15 lines

.mailmap Paul Burton <[email protected]> <[email protected]> · line 74

Quoted 12 lines
.mailmap +0 -0
index 1f7319b70b..35dddbe27b 100644
@@ -70,7 +70,9 @@ Paul Burton <[email protected]> 

<[email protected]>
  Paul Burton <[email protected]> <[email protected]> Paul Burton <[email protected]> <[email protected]> Paul Burton <[email protected]> <[email protected]>

.mailmap +2 -1
-Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>

I think this retroactively credits all your contributions to Linaro. Intentional?

Certainly not intentional. I was seeing this as a git limitation, but Alex pointed to me we are doing an invalid use of git-mailmap, since it is described as:

  ... the file .mailmap [...] is used to map author and committer names and email addresses to canonical real names and email addresses.

Quoted 6 lines

so more for typos, not developers changing email addresses. So our "replace old addresses by a more recent one" section might not be the best use. I think it was useful for the get_maintainer.pl fallback
option: when a file is not cover in MAINTAINERS then the script look at git history. If all files are well covered, then we shouldn't need this fallback anymore, nor this .mailmap translation.

Git's own .mailmap contains multiple "replace old addresses by a more recent one" entries. For example, the latest commit for that file is exactly for that purpose:
https://github.com/git/git/commit/4aa72ea1f64e8ddcd1865c76b24591c0916c0b5d

The situation looks same for .mailmap of Linux kernel too:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/.mailmap?id=1bb54043ff309795c90ccadd8a6e6b13ac40ec4e

My understanding is that Git's handling of .mailmap is designed to find out email addresses to be used to reach out. For example, someone may git-blame and find I wrote some buggy commit, and ask me to review a fix for it; in that case it is nicer if git-blame displays my latest contact point (@rsg.ci.i.u-tokyo.ac.jp) instead of one for my previous employer (@daynix.com), even though I authored the commit for Daynix.

Quoted 9 lines
Quoted 8 lines
Quoted 5 lines

+Philippe Mathieu-Daudé <[email protected]> <[email protected]> Stefan Brankovic <[email protected]> <[email protected]> Yongbok Kim <[email protected]> <[email protected]>

[...]

#6 lore raw
Quoted 55 lines · Akihiko Odaki
Quoted 38 lines · Philippe Mathieu-Daudé
Quoted 14 lines · Markus Armbruster
Quoted 12 lines · Philippe Mathieu-Daudé

The amsat.org domain is having issues with DMARC / SPF / DKIM:
https://lore.kernel.org/qemu-devel/
CAMVc7JUy5NeEN0q=4zfZvn_rppgqn9wicV1z=TsLuHKS3RY3Sw@mail.gmail.com/

Consolidate all of my MAINTAINERS entries on my work address.

---
  .mailmap    |  4 +++-
  MAINTAINERS | 62 ++++++++++++++++++++++++++---------------------------
  2 files changed, 34 insertions(+), 32 deletions(-)
Quoted 15 lines

.mailmap Paul Burton <[email protected]> <[email protected]> · line 74

Quoted 12 lines
.mailmap +0 -0
index 1f7319b70b..35dddbe27b 100644
@@ -70,7 +70,9 @@ Paul Burton <[email protected]>

<[email protected]>
Paul Burton <[email protected]> <[email protected]> Paul Burton <[email protected]> <[email protected]> Paul Burton <[email protected]> <[email protected]>

.mailmap +2 -1
-Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>

I think this retroactively credits all your contributions to Linaro. Intentional?

Certainly not intentional. I was seeing this as a git limitation, but Alex pointed to me we are doing an invalid use of git-mailmap, since it is described as:

... the file .mailmap [...] is used to map author and committer names and email addresses to canonical real names and email addresses.

Quoted 6 lines

so more for typos, not developers changing email addresses. So our "replace old addresses by a more recent one" section might not be the best use. I think it was useful for the get_maintainer.pl fallback
option: when a file is not cover in MAINTAINERS then the script look at git history. If all files are well covered, then we shouldn't need this fallback anymore, nor this .mailmap translation.

Git's own .mailmap contains multiple "replace old addresses by a more recent one" entries. For example, the latest commit for that file is exactly for that purpose:
https://github.com/git/git/commit/4aa72ea1f64e8ddcd1865c76b24591c0916c0b5d

The situation looks same for .mailmap of Linux kernel too:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/.mailmap?id=1bb54043ff309795c90ccadd8a6e6b13ac40ec4e

Quoted 7 lines

My understanding is that Git's handling of .mailmap is designed to find out email addresses to be used to reach out. For example, someone may git-blame and find I wrote some buggy commit, and ask me to review a fix for it; in that case it is nicer if git-blame displays my latest contact point (@rsg.ci.i.u-tokyo.ac.jp) instead of one for my previous employer (@daynix.com), even though I authored the commit for Daynix.

This is my understanding as well, it's not for employer attribution, it's for name change and/or email change.

People who wish to use git log for employer attribution reasons must use --no-mailmap. The original commit author in the tree does not go away!

Quoted 12 lines
Quoted 10 lines
Quoted 9 lines
Quoted 6 lines

+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
Stefan Brankovic <[email protected]>
<[email protected]>
Yongbok Kim <[email protected]> <[email protected]>

[...]

Signature · 2 lines
Manos Pitsidianakis
Emulation and Virtualization Engineer at Linaro Ltd
#7 lore raw
Quoted 65 lines · Manos Pitsidianakis
Quoted 55 lines · Akihiko Odaki
Quoted 38 lines · Philippe Mathieu-Daudé
Quoted 14 lines · Markus Armbruster
Quoted 12 lines · Philippe Mathieu-Daudé

The amsat.org domain is having issues with DMARC / SPF / DKIM:
https://lore.kernel.org/qemu-devel/
CAMVc7JUy5NeEN0q=4zfZvn_rppgqn9wicV1z=TsLuHKS3RY3Sw@mail.gmail.com/

Consolidate all of my MAINTAINERS entries on my work address.

---
  .mailmap    |  4 +++-
  MAINTAINERS | 62 ++++++++++++++++++++++++++---------------------------
  2 files changed, 34 insertions(+), 32 deletions(-)
Quoted 15 lines

.mailmap Paul Burton <[email protected]> <[email protected]> · line 74

Quoted 12 lines
.mailmap +0 -0
index 1f7319b70b..35dddbe27b 100644
@@ -70,7 +70,9 @@ Paul Burton <[email protected]>

<[email protected]>
Paul Burton <[email protected]> <[email protected]> Paul Burton <[email protected]> <[email protected]> Paul Burton <[email protected]> <[email protected]>

.mailmap +2 -1
-Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
+Philippe Mathieu-Daudé <[email protected]> <[email protected]>

I think this retroactively credits all your contributions to Linaro. Intentional?

Certainly not intentional. I was seeing this as a git limitation, but Alex pointed to me we are doing an invalid use of git-mailmap, since it is described as:

... the file .mailmap [...] is used to map author and committer names and email addresses to canonical real names and email addresses.

Quoted 6 lines

so more for typos, not developers changing email addresses. So our "replace old addresses by a more recent one" section might not be the best use. I think it was useful for the get_maintainer.pl fallback
option: when a file is not cover in MAINTAINERS then the script look at git history. If all files are well covered, then we shouldn't need this fallback anymore, nor this .mailmap translation.

Git's own .mailmap contains multiple "replace old addresses by a more recent one" entries. For example, the latest commit for that file is exactly for that purpose:
https://github.com/git/git/commit/4aa72ea1f64e8ddcd1865c76b24591c0916c0b5d

The situation looks same for .mailmap of Linux kernel too:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/.mailmap?id=1bb54043ff309795c90ccadd8a6e6b13ac40ec4e

Quoted 7 lines

My understanding is that Git's handling of .mailmap is designed to find out email addresses to be used to reach out. For example, someone may git-blame and find I wrote some buggy commit, and ask me to review a fix for it; in that case it is nicer if git-blame displays my latest contact point (@rsg.ci.i.u-tokyo.ac.jp) instead of one for my previous employer (@daynix.com), even though I authored the commit for Daynix.

Quoted 6 lines

This is my understanding as well, it's not for employer attribution, it's for name change and/or email change.

People who wish to use git log for employer attribution reasons must use --no-mailmap. The original commit author in the tree does not go away!

Shame there is no way to split the mailmap - because it is useful for identifying people with corrupted Author/email fields. I've fairly sure a bunch of entries were added in one of my clean-up passes while updating the giddm metadata.

Quoted 13 lines
Quoted 13 lines
Quoted 11 lines
Quoted 10 lines
Quoted 7 lines

+Philippe Mathieu-Daudé <[email protected]> <[email protected]>
Stefan Brankovic <[email protected]>
<[email protected]>
Yongbok Kim <[email protected]> <[email protected]>

[...]

Signature · 2 lines
Alex Bennée
Virtualisation Tech Lead @ Linaro
#8 lore raw
Quoted 10 lines · Alex Bennée
Quoted 3 lines · Manos Pitsidianakis

People who wish to use git log for employer attribution reasons must use --no-mailmap. The original commit author in the tree does not go away!

Shame there is no way to split the mailmap - because it is useful for identifying people with corrupted Author/email fields. I've fairly sure a bunch of entries were added in one of my clean-up passes while updating the giddm metadata.

It doesn't look like there's any way to say "for this command, use this other mailmap file" either -- there's a mailmap.file config setting, but it only lets you add an extra mailmap on top of the default, not override the default file...

-- PMM