From: Junio C Hamano <gitster@pobox.com> To: Jeff King <peff@peff.net> Cc: "Stefan Beller" <sbeller@google.com>, "Brandon Williams" <bmwill@google.com>, "git@vger.kernel.org" <git@vger.kernel.org>, "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, "Jonathan Nieder" <jrnieder@gmail.com>, "Ramsay Jones" <ramsay@ramsayjones.plus.com>, "Ben Peart" <peartben@gmail.com>, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com> Subject: Re: [PATCH v2 2/2] Makefile: add style build rule Date: Mon, 14 Aug 2017 16:29:56 -0700 [thread overview] Message-ID: <xmqqzib1sp6z.fsf@gitster.mtv.corp.google.com> (raw) In-Reply-To: <20170814225716.p5airw6j5o6dszbn@sigill.intra.peff.net> (Jeff King's message of "Mon, 14 Aug 2017 18:57:16 -0400") Jeff King <peff@peff.net> writes: > I suspect the "-p" version is going to be the one people invoke the most > often. Should it take the coveted "make style" slot, and the diff get > pushed off to another target? > > I was also confused at first that the "-p" version requires you to stage > the changes first. I don't know if we can make that less confusing via a > "make style". Or if it's just something people would get used to. But > sadly it makes the command not-quite orthogonal to "make test" in the > workflow. You can't "make style && make test && git add -p". You have > to add first, then check style, then you'd want to test that result to > make sure it didn't change the meaning of the code. Perhaps. By the way, I do not know which vintage of /usr/bin/git-clang-format I happen to have on my box, but I needed a crude workaround patch (attached at the end) to get it even run. The first thing it does is to call load_git_config() and it barfs because I have boolean configuration variables set to true in the correct way, which it does not seem to recognise. As to what it does, the first example I tried may not have been a great one. I got this: git clang-format --style file --diff --extensions c,h diff --git a/cache.h b/cache.h index 73e0085186..6462fe25bc 100644 --- a/cache.h +++ b/cache.h @@ -1498,11 +1498,8 @@ struct checkout { const char *base_dir; int base_dir_len; struct delayed_checkout *delayed_checkout; - unsigned force:1, - quiet:1, - not_new:1, - a_new_field:1, - refresh_cache:1; + unsigned force : 1, quiet : 1, not_new : 1, a_new_field : 1, + refresh_cache : 1; }; #define CHECKOUT_INIT { NULL, "" } which is not wrong per-se, but I have a mixed feelings. I do not want it to complain if the original tried to fit many items on a single line, but if the original wanted to have one item per line, I'd rather see it kept as-is. Anyway, we cannot have perfect checker from the day one, and considering this is an initial attempt, I'd say it is a good start. Thanks. diff --git a/git-clang-format b/git-clang-format index 60cd4fb25b..e8429b2750 100755 --- a/usr/bin/git-clang-format +++ b/usr/local/google/home/jch/g/Ubuntu-14.04-x86_64/gitstuff/bin/git-clang-format @@ -191,10 +191,13 @@ def load_git_config(non_string_options=None): out = {} for entry in run('git', 'config', '--list', '--null').split('\0'): if entry: - name, value = entry.split('\n', 1) - if name in non_string_options: - value = run('git', 'config', non_string_options[name], name) - out[name] = value + if '\n' in entry: + name, value = entry.split('\n', 1) + if name in non_string_options: + value = run('git', 'config', non_string_options[name], name) + out[name] = value + else: + out[entry] = "true"; return out
next prev parent reply other threads:[~2017-08-14 23:30 UTC|newest] Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-08-08 1:25 [RFC] clang-format: outline the git project's coding style Brandon Williams 2017-08-08 12:05 ` Johannes Schindelin 2017-08-08 17:40 ` Stefan Beller 2017-08-08 18:23 ` Brandon Williams 2017-08-09 22:33 ` Johannes Schindelin 2017-08-09 22:42 ` Stefan Beller 2017-08-10 9:38 ` Johannes Schindelin 2017-08-10 16:41 ` Junio C Hamano 2017-08-10 17:15 ` Brandon Williams 2017-08-10 17:28 ` Junio C Hamano 2017-08-10 21:30 ` Brandon Williams 2017-08-11 20:06 ` Ben Peart 2017-08-14 15:52 ` Johannes Schindelin 2017-09-28 11:41 ` Johannes Schindelin 2017-09-28 17:16 ` Brandon Williams 2017-08-08 17:45 ` Junio C Hamano 2017-08-08 18:03 ` Brandon Williams 2017-08-08 18:25 ` Junio C Hamano 2017-08-09 7:05 ` Junio C Hamano 2017-08-11 17:49 ` Brandon Williams 2017-08-11 19:00 ` Junio C Hamano 2017-08-09 13:01 ` Jeff King 2017-08-09 14:03 ` Ævar Arnfjörð Bjarmason 2017-08-09 22:53 ` Stefan Beller 2017-08-09 23:11 ` Stefan Beller 2017-08-11 17:52 ` Brandon Williams 2017-08-11 21:18 ` Jeff King 2017-08-12 4:39 ` Junio C Hamano 2017-08-13 4:41 ` Jeff King 2017-08-13 16:14 ` Ramsay Jones 2017-08-13 16:36 ` Ramsay Jones 2017-08-13 17:33 ` Junio C Hamano 2017-08-13 19:17 ` Ramsay Jones 2017-08-09 23:19 ` Jeff King 2017-08-15 0:40 ` brian m. carlson 2017-08-15 1:03 ` Jonathan Nieder 2017-08-14 21:30 ` [PATCH v2 0/2] clang-format Brandon Williams 2017-08-14 21:30 ` [PATCH v2 1/2] clang-format: outline the git project's coding style Brandon Williams 2017-08-14 22:02 ` Stefan Beller 2017-08-15 13:56 ` Ben Peart 2017-08-15 17:37 ` Brandon Williams 2017-08-14 22:48 ` Jeff King 2017-08-14 22:51 ` Jeff King 2017-08-14 22:54 ` Brandon Williams 2017-08-14 23:01 ` Jeff King 2017-08-16 12:18 ` Johannes Schindelin 2017-08-15 14:28 ` Ben Peart 2017-08-15 17:34 ` Brandon Williams 2017-08-15 17:41 ` Stefan Beller 2017-08-14 21:30 ` [PATCH v2 2/2] Makefile: add style build rule Brandon Williams 2017-08-14 21:53 ` Stefan Beller 2017-08-14 22:25 ` Junio C Hamano 2017-08-14 22:28 ` Stefan Beller 2017-08-14 22:57 ` Jeff King 2017-08-14 23:29 ` Junio C Hamano [this message] 2017-08-14 23:47 ` Junio C Hamano 2017-08-15 0:05 ` Brandon Williams 2017-08-15 1:52 ` Jeff King 2017-08-14 21:32 ` [PATCH v2 0/2] clang-format Brandon Williams 2017-08-14 23:06 ` Jeff King 2017-08-14 23:15 ` Stefan Beller 2017-08-15 1:47 ` Jeff King 2017-08-15 3:03 ` Junio C Hamano 2017-08-15 3:38 ` Jeff King
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=xmqqzib1sp6z.fsf@gitster.mtv.corp.google.com \ --to=gitster@pobox.com \ --cc=Johannes.Schindelin@gmx.de \ --cc=avarab@gmail.com \ --cc=bmwill@google.com \ --cc=git@vger.kernel.org \ --cc=jrnieder@gmail.com \ --cc=peartben@gmail.com \ --cc=peff@peff.net \ --cc=ramsay@ramsayjones.plus.com \ --cc=sbeller@google.com \ --subject='Re: [PATCH v2 2/2] Makefile: add style build rule' \ /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
Code repositories for project(s) associated with this 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).