From: Ryan Anderson <ryan@michonline.com>
To: Andreas Ericsson <ae@op5.se>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-send-mail in sh
Date: Sun, 27 Nov 2005 19:49:05 -0500 [thread overview]
Message-ID: <438A5401.3070008@michonline.com> (raw)
In-Reply-To: <43874415.8040302@op5.se>
[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]
Andreas Ericsson wrote:
> Ryan Anderson wrote:
>
>> On Fri, Nov 25, 2005 at 10:45:41AM +0100, Andreas Ericsson wrote:
>>
>>> Finally giving up on git-send-email (I won't install the 6
>>> perl-modules it requires and I don't know perl enough to remove the
>>> need for them), I hacked up a replacement in sh. It's more aptly
>>> named as well. ;)
>>
>> Scanning the list, 2 are related to option handling (one of which is
>> builtin), one isn't used (Data::Dumper), and two are related to sending
>> valid emails.
>
> When I try to install Email::Valid (using apt) it wants an additional
> two modules. Mail::Sendmail wants one other, so that's Data::Dumper, the
> two actually used and the three those two use. Six, for short.
Can I ask why you aren't willing to install packages, such as those? I
can understand a reluctance to install modules directly from CPAN, on an
otherwise package-managed system, but I'm afraid I must confess to
puzzlement over a reluctance to use pre-packaged modules.
The major flaw in git-send-email, from my perspective, was a lack of
support for SMTP AUTH, for situations like Junio's, where the local MTA
(and thus "mail" as well) are not configured to handle SMTP AUTH. Moving
to a purely shell based replacement seems to make this an even harder
feature to support. (Though, admittedly, I haven't even made an attempt
to add it to the Perl version yet.)
>> The email address verification is ridiculously hard to get
>> correct, so using pre-written code for that seemed justified.
>>
>
> But it isn't necessary to validate it to such exactness. Nothing worse
> will happen than the user chiding himself for his butterfingers if
> he/she makes a mistake.
>
> Besides, I think typos are by far the most common error. Those are
> usually valid email addresses while still not being correct.
Fair enough.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-11-28 0:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 9:45 git-send-mail in sh Andreas Ericsson
2005-11-25 10:12 ` Nikolai Weibull
2005-11-25 10:59 ` Andreas Ericsson
2005-11-25 11:06 ` Fernando J. Pereda
2005-11-25 11:05 ` Johannes Schindelin
2005-11-25 14:25 ` Andreas Ericsson
2005-11-25 17:20 ` A Large Angry SCM
2005-11-25 11:15 ` Junio C Hamano
2005-11-25 17:26 ` Andreas Ericsson
2005-11-25 18:30 ` Junio C Hamano
2005-11-26 22:35 ` Andreas Ericsson
2005-11-27 22:01 ` Junio C Hamano
2005-11-27 23:34 ` Andreas Ericsson
2005-11-28 0:15 ` Nikolai Weibull
2005-11-26 20:12 ` Junio C Hamano
2005-11-26 23:34 ` Yann Dirson
2005-11-25 16:33 ` Ryan Anderson
2005-11-25 17:04 ` Andreas Ericsson
2005-11-28 0:49 ` Ryan Anderson [this message]
2005-11-28 9:02 ` Andreas Ericsson
2005-11-28 9:34 ` Junio C Hamano
2005-11-29 13:04 ` Andreas Ericsson
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=438A5401.3070008@michonline.com \
--to=ryan@michonline.com \
--cc=ae@op5.se \
--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).