From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Luke Diamand <luke@diamand.org>, Git Users <git@vger.kernel.org>
Subject: Re: [PATCH v8 0/7] git-p4: add support for large file systems
Date: Sun, 4 Oct 2015 11:15:31 -0700 [thread overview]
Message-ID: <DD450E04-582C-498A-92D8-D6A78ECB30F1@gmail.com> (raw)
In-Reply-To: <xmqqd1wv3lyc.fsf@gitster.mtv.corp.google.com>
On 03 Oct 2015, at 10:23, Junio C Hamano <gitster@pobox.com> wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Luke Diamand <luke@diamand.org> writes:
>>
>>> All looks good to me, Ack.
>>>
>>> One tiny thing perhaps Junio could comment on: the git commit message
>>> for 75abe9fa5b39980de27dfc33dd5b4f4b5926f34c, "git-p4: add optional
>>> type specifier to gitConfig reader" uses what looks like UTF-8 encoded
>>> left and right quotes, rather than regular ASCII quotes ("). I don't
>>> know if that matters.
>>
>> Yeah, I noticed them, too. In general, I'd prefer to avoid these
>> pretty-quotes myself, as they typically do not add much information
>> (unless nesting matters, which is usually not the case in the log
>> message, or something) and the primary effect of them is to force us
>> to step outside ASCII, which causes editors and pagers to misalign
>> for some people.
>>
>> But it is not too huge an issue that it is worth to go back and fix
>> them, either.
>
> Well, I looked at it again and it also replaced double-dash before
> option names like --bool and --int with something funny (are these
> em-dashes?), which is a more serious bogosity than pretty quotes, so
> I ended up amending the message for that commit after all.
>
Oh. This was not intentional. I wonder how that happened. I will watch out for it in the future.
Thanks for fixing,
Lars
prev parent reply other threads:[~2015-10-04 18:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 7:54 [PATCH v8 0/7] git-p4: add support for large file systems larsxschneider
2015-09-26 7:54 ` [PATCH v8 1/7] git-p4: add optional type specifier to gitConfig reader larsxschneider
2015-09-26 7:54 ` [PATCH v8 2/7] git-p4: add gitConfigInt reader larsxschneider
2015-09-26 7:55 ` [PATCH v8 3/7] git-p4: return an empty list if a list config has no values larsxschneider
2015-09-26 7:55 ` [PATCH v8 4/7] git-p4: add file streaming progress in verbose mode larsxschneider
2015-09-26 7:55 ` [PATCH v8 5/7] git-p4: check free space during streaming larsxschneider
2015-09-26 7:55 ` [PATCH v8 6/7] git-p4: add support for large file systems larsxschneider
2015-09-26 7:55 ` [PATCH v8 7/7] git-p4: add Git LFS backend for large file system larsxschneider
2015-09-28 19:55 ` [PATCH v8 0/7] git-p4: add support for large file systems Junio C Hamano
2015-10-03 16:27 ` Luke Diamand
2015-10-03 17:17 ` Junio C Hamano
2015-10-03 17:23 ` Junio C Hamano
2015-10-04 18:15 ` Lars Schneider [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DD450E04-582C-498A-92D8-D6A78ECB30F1@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=luke@diamand.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).