From: Alex Kuleshov <kuleshovmail@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Alexander Kuleshov <kuleshovmail@gmail.com>,
git@vger.kernel.org, Thomas Gummerer <t.gummerer@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH v3] send-email: Improve format of smtp initialization error message
Date: Tue, 30 Dec 2014 16:59:04 +0600 [thread overview]
Message-ID: <87iogt4d53.fsf@gmail.com> (raw)
In-Reply-To: <xmqqppb2z3w9.fsf@gitster.dls.corp.google.com>
What's about output like this:
Unable to initialize SMTP properly. Check config and use --smtp-debug.
VALUES:
server=smtp.gmail.com
encryption=
hello=localhost.localdomain
port=587
Junio C Hamano <gitster@pobox.com> @ 2014-12-30 00:50 QYZT:
> Alexander Kuleshov <kuleshovmail@gmail.com> writes:
>
>> Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
>> ---
>> git-send-email.perl | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/git-send-email.perl b/git-send-email.perl
>> index 82c6fea..60dcd8d 100755
>> --- a/git-send-email.perl
>> +++ b/git-send-email.perl
>> @@ -1275,10 +1275,10 @@ X-Mailer: git-send-email $gitversion
>>
>> if (!$smtp) {
>> die "Unable to initialize SMTP properly. Check config and use --smtp-debug. ",
>> - "VALUES: server=$smtp_server ",
>> - "encryption=$smtp_encryption ",
>> - "hello=$smtp_domain",
>> - defined $smtp_server_port ? " port=$smtp_server_port" : "";
>> + "\nVALUES: \n\tserver=$smtp_server ",
>> + "\n\tencryption=$smtp_encryption ",
>> + "\n\thello=$smtp_domain",
>> + defined $smtp_server_port ? " \n\tport=$smtp_server_port" : "";
>
> It may be a good convention to have LF at the beginning of a new
> string (i.e. we terminate the old line only when we have something
> more to say), but that is true only when we want to end the sentence
> without the final newline. I wonder if that is true in this case;
> do we want perl to say "at line # in file X" at the end?
>
> In any case, you have two output lines that ends with a trailing SP
> just before LF, which is probably not what you wanted.
>
> If we want to see all lines end with LF, it may be far easier to
> read this way:
>
> die "msg\n",
> "\tvar1=val1\n",
> "\tvar2=val2\n",
> defined $var3 ? "\tvar3=val3\n" : "";
>
> I dunno.
--
Best regards.
0xAX
next prev parent reply other threads:[~2014-12-30 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 17:53 [PATCH v3] send-email: Improve format of smtp initialization error message Alexander Kuleshov
2014-12-29 18:50 ` Junio C Hamano
2014-12-30 10:59 ` Alex Kuleshov [this message]
2014-12-30 16:13 ` Junio C Hamano
2015-01-04 9:39 ` Alexander Kuleshov
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=87iogt4d53.fsf@gmail.com \
--to=kuleshovmail@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.com \
--cc=t.gummerer@gmail.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).