{"thread":{"id":"9177","subject":"git-send-email and pine alias format","startedAt":"2007-07-23T16:49:29Z","lastAt":"2007-07-24T14:51:06Z","messageCount":3,"participants":["Kumar Gala","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"48315","messageId":"Pine.LNX.4.64.0707231146160.6889@blarg.am.freescale.net","threadId":"9177","inReplyTo":null,"subject":"git-send-email and pine alias format","fromName":"Kumar Gala","fromEmail":"galak@kernel.crashing.org","sentAt":"2007-07-23T16:49:29Z","receivedAt":"2007-07-23T16:49:29Z","isPatch":false,"sender":{"key":"galak@kernel.crashing.org","avatar":null},"body":"I was wondering why we don't parse the pine alias format according to the\nfollowing spec:\n\nhttp://www.washington.edu/pine/tech-notes/low-level.html\n\nI'd expect omething like, to get the address field.\n\n@@ -225,7 +238,7 @@ my %parse_alias = (\n                        $aliases{$1} = [ split(/\\s+/, $2) ];\n                }}},\n        pine => sub { my $fh = shift; while (<$fh>) {\n-               if (/^(\\S+)\\t.*\\t(.*)$/) {\n+               if (/^(\\S+)\\s+(.*)$/) {\n                        $aliases{$1} = [ split(/\\s*,\\s*/, $2) ];\n                }}},\n        gnus => sub { my $fh = shift; while (<$fh>) {\n\n- k\n"},{"id":"48398","messageId":"7vodi2i97j.fsf@assigned-by-dhcp.cox.net","threadId":"9177","inReplyTo":"Pine.LNX.4.64.0707231146160.6889@blarg.am.freescale.net","subject":"Re: git-send-email and pine alias format","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-07-24T06:53:20Z","receivedAt":"2007-07-24T06:53:20Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Kumar Gala <galak@kernel.crashing.org> writes:\n\n> I was wondering why we don't parse the pine alias format according to the\n> following spec:\n>\n> http://www.washington.edu/pine/tech-notes/low-level.html\n>\n> I'd expect something like, to get the address field.\n\nMy guess is simply because we got a \"works-for-us\" regexp by\nobserving the program's behaviour, done by real Pine users.  On\ntop of that, probably nobody knew and/or bothered to check if\nthere is such \"official spec\" available.\n\nCould you send a signed and testable patch to the list so other\nPine users can try it out please?  After seeing a few Ack's on\nthe list, I'd like to apply it and preferably do so before 1.5.3\nfinal.\n"},{"id":"48476","messageId":"Pine.LNX.4.64.0707240950530.19035@blarg.am.freescale.net","threadId":"9177","inReplyTo":"7vodi2i97j.fsf@assigned-by-dhcp.cox.net","subject":"Re: git-send-email and pine alias format","fromName":"Kumar Gala","fromEmail":"galak@kernel.crashing.org","sentAt":"2007-07-24T14:51:06Z","receivedAt":"2007-07-24T14:51:06Z","isPatch":false,"sender":{"key":"galak@kernel.crashing.org","avatar":null},"body":"On Mon, 23 Jul 2007, Junio C Hamano wrote:\n\n> Kumar Gala <galak@kernel.crashing.org> writes:\n>\n> > I was wondering why we don't parse the pine alias format according to the\n> > following spec:\n> >\n> > http://www.washington.edu/pine/tech-notes/low-level.html\n> >\n> > I'd expect something like, to get the address field.\n>\n> My guess is simply because we got a \"works-for-us\" regexp by\n> observing the program's behaviour, done by real Pine users.  On\n> top of that, probably nobody knew and/or bothered to check if\n> there is such \"official spec\" available.\n>\n> Could you send a signed and testable patch to the list so other\n> Pine users can try it out please?  After seeing a few Ack's on\n> the list, I'd like to apply it and preferably do so before 1.5.3\n> final.\n\nOk, done.\n\n- k\n"}]}