git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sean Allred <allred.sean@gmail.com>
Cc: Philip Oakley <philipoakley@iee.email>,
	rsbecker@nexbridge.com, git@vger.kernel.org, sallred@epic.com,
	grmason@epic.com, sconrad@epic.com
Subject: Re: Dealing with corporate email recycling
Date: Sun, 13 Mar 2022 23:16:24 +0000	[thread overview]
Message-ID: <xmqqtuc1tpdj.fsf@gitster.g> (raw)
In-Reply-To: <87ilsha2b7.fsf@gmail.com> (Sean Allred's message of "Sun, 13 Mar 2022 17:40:47 -0500")

Sean Allred <allred.sean@gmail.com> writes:

> rather than use magic comments :-) Adapting to your suggestion, this
> might look like the following:
>
>     A. U. Thor <foo@example.com> <ada.example.com> <[ approxidate ]>

You'd probably want a timerange (valid-from and valid-to), instead
of one single timestamp?

Because at least three valid forms of mailmap entries should be
understood by the current generation of mailmap readers, i.e.

    Human Readable Name <e-mail@add.re.ss>
    Right Name <right@add.re.ss> <wrong@add.re.ss>
    Right Name <right@add.re.ss> Wrong Name <wrong@add.re.ss>

the extended entry format to record the validity timerange should
be chosen to cause parsers that are prepared to take these three
kinds of lines to barf and ignore.

  reply	other threads:[~2022-03-13 23:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-12 22:38 Dealing with corporate email recycling Sean Allred
2022-03-13  0:03 ` Junio C Hamano
2022-03-13  0:26   ` rsbecker
2022-03-13 14:01     ` Sean Allred
2022-03-13 14:20       ` rsbecker
2022-03-13 14:41         ` Sean Allred
2022-03-13 15:02           ` rsbecker
2022-03-13 15:21             ` Sean Allred
2022-03-13 19:57               ` Philip Oakley
2022-03-13 22:40                 ` Sean Allred
2022-03-13 23:16                   ` Junio C Hamano [this message]
2022-03-13 23:23                     ` rsbecker
2022-03-14  0:19                       ` Junio C Hamano
2022-03-14 11:56                     ` Philip Oakley
2022-03-14 21:24                       ` Junio C Hamano
2022-03-14 22:25                         ` Philip Oakley
2022-03-15  1:23                       ` Sean Allred
2022-03-15 11:15                         ` Philip Oakley
2022-03-13 12:20 ` Philip Oakley
2022-03-13 13:35   ` Sean Allred
2022-03-14 11:59     ` Philip Oakley
2022-03-13 15:51 ` Ævar Arnfjörð Bjarmason
2022-03-13 17:22 ` brian m. carlson
2022-03-13 17:52   ` rsbecker
2022-03-13 19:47     ` rsbecker
2022-03-13 22:23       ` Sean Allred
2022-03-15  1:27 ` Sean Allred
2022-03-18 21:22 ` Peter Krefting

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqtuc1tpdj.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=allred.sean@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=grmason@epic.com \
    --cc=philipoakley@iee.email \
    --cc=rsbecker@nexbridge.com \
    --cc=sallred@epic.com \
    --cc=sconrad@epic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).