From: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
To: kusmabite@gmail.com
Cc: "Torsten Bögershausen" <tboegi@web.de>, git@vger.kernel.org
Subject: Re: [PATCH v2] Allow git mv FileA fILEa on case ignore file systems
Date: Sat, 19 Mar 2011 20:30:46 +0100 [thread overview]
Message-ID: <4D850466.8040909@gmail.com> (raw)
In-Reply-To: <AANLkTimfk8bb-V8Br+KKpoLbA3G3y9HxyfjA=NrsgR0v@mail.gmail.com>
W dniu 19.03.2011 19:20, Erik Faye-Lund pisze:
> 2011/3/19 Torsten Bögershausen <tboegi@web.de>:
>> + if (!(GetFileInformationByHandle(h,&hia)))
>> + return 0;
>> + CloseHandle(h);
>
> Indentation-slip?
I suspect so. CloseHandle line does not use tabs.
Out of curiosity I've roughly counted number of lines that have
correct and incorrect indentation.
About 8% (~12600 out of 151000 indented lines) are incorrectly indented.
Don't know if that good or bad :)
I have used following to get the numbers:
Bad indentation (includes "Correctly indented comments"):
git$ TAB="`echo -e '\t'`" && grep -E "^[ $TAB]* [ $TAB]*[^ $TAB]" *.sh *.[ch] */*.sh */*.[ch] | wc -l
22495
Correctly indented comments:
git$ TAB="`echo -e '\t'`" && grep -E "^[ $TAB]* [*]" *.sh *.[ch] */*.sh */*.[ch] | wc -l
9911
Good indentation (does not include "Correctly indented comments"):
git$ TAB="`echo -e '\t'`" && grep -E "^$TAB+[^ $TAB]" *.sh *.[ch] */*.sh */*.[ch] | wc -l
128173
--
Piotr Krukowiecki
next prev parent reply other threads:[~2011-03-19 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 14:28 [PATCH v2] Allow git mv FileA fILEa on case ignore file systems Torsten Bögershausen
2011-03-19 18:20 ` Erik Faye-Lund
2011-03-19 19:30 ` Piotr Krukowiecki [this message]
2011-03-20 5:50 ` Junio C Hamano
2011-04-10 5:48 ` Torsten Bögershausen
2011-04-11 16:55 ` Junio C Hamano
2011-04-11 20:05 ` Torsten Bögershausen
2011-04-12 6:16 ` Johannes Sixt
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=4D850466.8040909@gmail.com \
--to=piotr.krukowiecki@gmail.com \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=tboegi@web.de \
/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).