From: Kumar Gala <galak@kernel.crashing.org>
To: git@vger.kernel.org
Subject: git-send-email and pine alias format
Date: Mon, 23 Jul 2007 11:49:29 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707231146160.6889@blarg.am.freescale.net> (raw)
I was wondering why we don't parse the pine alias format according to the
following spec:
http://www.washington.edu/pine/tech-notes/low-level.html
I'd expect omething like, to get the address field.
@@ -225,7 +238,7 @@ my %parse_alias = (
$aliases{$1} = [ split(/\s+/, $2) ];
}}},
pine => sub { my $fh = shift; while (<$fh>) {
- if (/^(\S+)\t.*\t(.*)$/) {
+ if (/^(\S+)\s+(.*)$/) {
$aliases{$1} = [ split(/\s*,\s*/, $2) ];
}}},
gnus => sub { my $fh = shift; while (<$fh>) {
- k
next reply other threads:[~2007-07-23 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 16:49 Kumar Gala [this message]
2007-07-24 6:53 ` git-send-email and pine alias format Junio C Hamano
2007-07-24 14:51 ` Kumar Gala
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=Pine.LNX.4.64.0707231146160.6889@blarg.am.freescale.net \
--to=galak@kernel.crashing.org \
--cc=git@vger.kernel.org \
/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).