git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Ryan Anderson <ryan@michonline.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script
Date: Sun, 31 Jul 2005 17:40:18 -0700	[thread overview]
Message-ID: <7vk6j6a3rh.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050731235242.GH32263@mythryan2.michonline.com> (Ryan Anderson's message of "Sun, 31 Jul 2005 19:52:42 -0400")

Ryan Anderson <ryan@michonline.com> writes:

> If I hope that nobody has done something like:
> 	GIT_AUTHOR="Ryan <> Anderson"
> 	GIT_AUTHOR_EMAIL="ryan@michonline.com"
>
> I get more confusing results.

The function git_author_info() would remove <> from the above
GIT_AUTHOR_* environment values by calling ident.c:copy(), so I
think you would get more-or-less what you _should_ expect without
getting confused.

    $ GIT_AUTHOR_NAME="Ryan <> Anderson" \
      GIT_AUTHOR_EMAIL="ryan@michonline.com" git-var -l
    GIT_COMMITTER_IDENT=Junio C Hamano <junkio@cox.net> 1122855849 -0700
    GIT_AUTHOR_IDENT=Ryan  Anderson <ryan@michonline.com> 1122855849 -0700

>> Is this the culprit that produced this mechanical-looking line?
>> 
>>     To: junkio@cox.net,git@vger.kernel.org
>
> No, that line was exactly what I put into the readline entry.

I was mostly talking about Email::Valid seeming to be stripping
out the display-name[*] part and keeping only addr-spec[*] part,
like this:

    $ cat j.perl
    #!/usr/bin/perl
    use Email::Valid;
    for ('Junio C Hamano <junkio@cox.net>',
         'Ryan Anderson <ryan@michonline.com>') {
        print $_, " => ", lc(Email::Valid->address($_)), "\n";
    }
    $ perl j.perl
    Junio C Hamano <junkio@cox.net> => junkio@cox.net
    Ryan Anderson <ryan@michonline.com> => ryan@michonline.com

Also, I wonder if running lc() to downcase the local-part[*] is
safe/allowed/correct; domain[*] part is case insensitive and
should be OK to downcase, though.

> ..., because of the way I pull in all the relevant emails
> from various places.  So I really needed a way to cull the duplicates.
> ...  I could do soemthing like this, instead, I suppose:

I understand your needs, and you can make it a "sub
filter_dups", which I think would make things a lot more
pleasant to read.


[Footnote]

Terms marked [*] are from RFC2822, section 3.4.

  reply	other threads:[~2005-08-01  0:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31  8:17 [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-07-31  8:17 ` [PATCH 2/3] Add documentation for git-send-email-script Ryan Anderson
2005-07-31  8:17   ` [PATCH 3/3] Add new dependencies caused by git-send-email-script to debian/control Ryan Anderson
2005-07-31  8:24 ` [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-07-31  9:36   ` Matthias Urlichs
2005-07-31  9:45 ` Junio C Hamano
2005-07-31 19:13   ` Junio C Hamano
2005-07-31 23:52   ` Ryan Anderson
2005-08-01  0:40     ` Junio C Hamano [this message]
2005-08-01  7:59       ` Matthias Urlichs
     [not found]     ` <20050801220800.GA12331@uglybox.localnet>
     [not found]       ` <20050801224308.GB12331@uglybox.localnet>
     [not found]         ` <7vk6j52qhn.fsf_-_@assigned-by-dhcp.cox.net>
2005-08-02 12:48           ` [OT] Perl-ish perl vs. C-ish perl Noel Maddy
2005-08-02 16:37             ` Junio C Hamano
2005-08-02 17:20               ` Noel Maddy
2005-08-03  1:30   ` [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-08-03  7:32     ` Matthias Urlichs
2005-07-31 10:25 ` Johannes Schindelin
2005-07-31 23:54   ` Ryan Anderson
2005-07-31 10:50 ` Sergey Vlasov

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=7vk6j6a3rh.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=ryan@michonline.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).