From: Heiko Voigt <hvoigt@hvoigt.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
Phil Hord <phil.hord@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Michael J Gruber <git@drmicha.warpmail.net>,
Marc Branchaud <marcnarc@xiplink.com>,
"W. Trevor King" <wking@tremily.us>
Subject: Re: [PATCH v6] submodule: add 'deinit' command
Date: Wed, 6 Mar 2013 07:52:46 +0100 [thread overview]
Message-ID: <20130306065246.GB4064@sandbox-ub> (raw)
In-Reply-To: <7vppzdvoj1.fsf@alter.siamese.dyndns.org>
On Tue, Mar 05, 2013 at 07:45:22AM -0800, Junio C Hamano wrote:
> Heiko Voigt <hvoigt@hvoigt.net> writes:
>
> >> + if test -z "$force"
> >> + then
> >> + git rm -n "$sm_path" ||
> >> + die "$(eval_gettext "Submodule work tree '\$sm_path' contains local modifications; use '-f' to discard them")"
> >
> > Minor nit. IMO, there is an indentation for the || missing here. Maybe
> > Junio can squash that in on his side?
>
> Sorry, but I do not see an indentation nit here. The format looks
> perfectly sane to me and in fact any other indentation would be
> wrong.
>
> Puzzled...
Wouldn't you write this code snippet like this to make clear that there
is another conditional?
if test -z "$force"
then
git rm -n "$sm_path" ||
die "$(eval_gettext "Submodule work tree '\$sm_path' contains local modifications; use '-f' to discard them")"
It seems it is not clear in the code base either. Some places do
some do not indent:
git grep -A 1 '||' *.sh
Except for the testsuite I just assumed that this style was common,
because for me it makes the code much easier to read.
It seems it is not, so forget my comment.
Cheers Heiko
next prev parent reply other threads:[~2013-03-06 6:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 21:11 [PATCH v4] submodule: add 'deinit' command Jens Lehmann
2013-02-12 17:11 ` Phil Hord
2013-02-12 18:03 ` Junio C Hamano
2013-02-13 19:33 ` Jens Lehmann
2013-02-13 19:56 ` Junio C Hamano
2013-02-17 20:06 ` [PATCH v5] " Jens Lehmann
2013-02-17 22:32 ` Junio C Hamano
2013-02-18 19:20 ` Jens Lehmann
2013-03-04 21:20 ` [PATCH v6] " Jens Lehmann
2013-03-05 7:29 ` Heiko Voigt
2013-03-05 15:45 ` Junio C Hamano
2013-03-06 6:52 ` Heiko Voigt [this message]
2013-03-12 15:39 ` [PATCH v4] " Phil Hord
2013-03-12 16:22 ` Junio C Hamano
2013-03-18 20:54 ` Jens Lehmann
2013-03-19 1:45 ` Junio C Hamano
2013-04-01 19:02 ` [PATCH] submodule deinit: clarify work tree removal message Jens Lehmann
2013-04-16 13:32 ` Phil Hord
2013-04-16 20:47 ` [PATCH] submodule deinit: don't output "Cleared directory" when directory is empty Jens Lehmann
2013-04-17 5:16 ` [PATCH] submodule deinit: clarify work tree removal message Junio C Hamano
2013-04-17 20:30 ` Jens Lehmann
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=20130306065246.GB4064@sandbox-ub \
--to=hvoigt@hvoigt.net \
--cc=Jens.Lehmann@web.de \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marcnarc@xiplink.com \
--cc=phil.hord@gmail.com \
--cc=wking@tremily.us \
/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).