From: Junio C Hamano <gitster@pobox.com>
To: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH v5 0/3] git-remote-fd & git-remote-ext
Date: Fri, 08 Oct 2010 12:56:51 -0700 [thread overview]
Message-ID: <7vtykwv4os.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1286563200-7270-1-git-send-email-ilari.liusvaara@elisanet.fi> (Ilari Liusvaara's message of "Fri\, 8 Oct 2010 21\:39\:57 +0300")
Every time I queued this series, I've been fixing up styles without
complaining. It is boring and in general not very fun to spend time
fixing style violations, and the worst part of the story is that by the
time I am done, I don't have time left for addressing issues in the
substance of the patch or energy and concentration required for handling
patches from other people.
I think I probably should have complained earlier. I am assuming that you
are rewriting and rebasing, so once they are fixed at your end, I will
hopefully have to re-fix everything over and over again in the future
round.
Could you fix these up at your end please?
ERROR: space required before the open parenthesis '('
#216: FILE: transport-helper.c:990:
+ while(t->state != SSTATE_FINISHED) {
ERROR: "foo* bar" should be "foo *bar"
#596: FILE: builtin/remote-fd.c:58:
+ char* end;
ERROR: spaces required around that '!=' (ctx:WxV)
#603: FILE: builtin/remote-fd.c:65:
+ if ((end == argv[2]) || (*end != ',' && *end !='/' && *end))
^
ERROR: "foo* bar" should be "foo *bar"
#609: FILE: builtin/remote-fd.c:71:
+ char* end2;
ERROR: spaces required around that '!=' (ctx:WxV)
#612: FILE: builtin/remote-fd.c:74:
+ if ((end2 == end + 1) || (*end2 !='/' && *end2))
^
ERROR: do not initialise globals to 0 or NULL
#897: FILE: builtin/remote-ext.c:24:
+char* git_req = NULL;
ERROR: "foo* bar" should be "foo *bar"
#897: FILE: builtin/remote-ext.c:24:
+char* git_req = NULL;
ERROR: do not initialise globals to 0 or NULL
#898: FILE: builtin/remote-ext.c:25:
+char* git_req_vhost = NULL;
ERROR: "foo* bar" should be "foo *bar"
#898: FILE: builtin/remote-ext.c:25:
+char* git_req_vhost = NULL;
ERROR: space required before the open parenthesis '('
#959: FILE: builtin/remote-ext.c:86:
+ switch(str[rpos]) {
ERROR: space required before the open parenthesis '('
#973: FILE: builtin/remote-ext.c:100:
+ switch(str[rpos]) {
ERROR: space required before the open parenthesis '('
#983: FILE: builtin/remote-ext.c:110:
+ switch(special) {
ERROR: "foo** bar" should be "foo **bar"
#1002: FILE: builtin/remote-ext.c:129:
+ char** ret;
ERROR: "foo* bar" should be "foo *bar"
#1006: FILE: builtin/remote-ext.c:133:
+ char* ret;
ERROR: "(foo*)" should be "(foo *)"
#1014: FILE: builtin/remote-ext.c:141:
+ ret = xcalloc(arguments + 1, sizeof(char*));
ERROR: "(foo**)" should be "(foo **)"
#1018: FILE: builtin/remote-ext.c:145:
+ return (const char**)ret;
ERROR: "foo* bar" should be "foo *bar"
#1026: FILE: builtin/remote-ext.c:153:
+ char* buffer;
total: 17 errors, 0 warnings, 851 lines checked
next prev parent reply other threads:[~2010-10-08 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 18:39 [RFC PATCH v5 0/3] git-remote-fd & git-remote-ext Ilari Liusvaara
2010-10-08 18:39 ` [RFC PATCH v5 1/3] Add bidirectional_transfer_loop() Ilari Liusvaara
2010-10-08 18:39 ` [RFC PATCH v5 2/3] git-remote-fd Ilari Liusvaara
2010-10-08 18:40 ` [RFC PATCH v5 3/3] git-remote-ext Ilari Liusvaara
2010-10-08 19:56 ` Junio C Hamano [this message]
2010-10-08 20:07 ` [RFC PATCH v5 0/3] git-remote-fd & git-remote-ext Pat Notz
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=7vtykwv4os.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
/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).