git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-send-email and pine alias format

From
KGKumar Gala <galak@kernel.crashing.org>
Date
Jul 23, 2007, 16:49 UTC
Message-ID
<Pine.LNX.4.64.0707231146160.6889@blarg.am.freescale.net>

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: Junio C Hamano
Message 1 of 3 in “git-send-email and pine alias format”
  1. Kumar GalaJul 23, 2007
  2. Junio C HamanoJul 24, 2007
  3. Kumar GalaJul 24, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.