From: Mike Crowe <mac@mcrowe.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] push: add recurseSubmodules config option
Date: Mon, 30 Nov 2015 19:00:21 +0000 [thread overview]
Message-ID: <20151130190021.GA29232@mcrowe.com> (raw)
In-Reply-To: <xmqqa8pv8hkx.fsf@gitster.mtv.corp.google.com>
On Monday 30 November 2015 at 10:31:26 -0800, Junio C Hamano wrote:
> Mike Crowe <mac@mcrowe.com> writes:
>
> > diff --git a/builtin/push.c b/builtin/push.c
> > index 3bda430..dfced74 100644
> > --- a/builtin/push.c
> > +++ b/builtin/push.c
> > @@ -9,6 +9,7 @@
> > #include "transport.h"
> > #include "parse-options.h"
> > #include "submodule.h"
> > +#include "submodule-config.h"
> > #include "send-pack.h"
> >
> > static const char * const push_usage[] = {
> > @@ -20,7 +21,7 @@ static int thin = 1;
> > static int deleterefs;
> > static const char *receivepack;
> > static int verbosity;
> > -static int progress = -1;
> > +static int progress = -1, recurse_submodules = RECURSE_SUBMODULES_DEFAULT;
>
> One variable per line, please. Especially when the two variables do
> not have anything to do with each other, and do not have any logical
> similarity between them.
I wouldn't normally have done that either, but I was mirroring the
equivalent code in fetch.c. I will change it.
> > @@ -452,22 +453,15 @@ static int do_push(const char *repo, int flags)
> > static int option_parse_recurse_submodules(const struct option *opt,
> > const char *arg, int unset)
> > {
> > - int *flags = opt->value;
> > + int *recurse_submodules = opt->value;
> >
> > - if (*flags & (TRANSPORT_RECURSE_SUBMODULES_CHECK |
> > - TRANSPORT_RECURSE_SUBMODULES_ON_DEMAND))
> > + if (*recurse_submodules != RECURSE_SUBMODULES_DEFAULT)
> > die("%s can only be used once.", opt->long_name);
>
> The usual convention thoughout Git user experience is "the last one
> wins" (both in the configuration and in the command line options).
> Is there a good reason to deviate from that here?
I was aiming to retain the existing behaviour, which was to complain if
conflicting options were supplied on the command line. Making the last one
win would have been rather simpler. I can change this too, unless someone
knows why complaining about conflicting options would be useful.
Note that I previously sent an updated patch as
<1447758356-7727-1-git-send-email-mac@mcrowe.com> but I believe that your
criticisms still apply.
Thanks for the review.
Mike.
prev parent reply other threads:[~2015-11-30 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 13:24 [PATCH] push: add recurseSubmodules config option Mike Crowe
2015-11-16 18:15 ` Stefan Beller
2015-11-16 18:31 ` Mike Crowe
2015-11-16 19:05 ` Jens Lehmann
2015-11-16 23:13 ` Eric Sunshine
2015-11-30 18:31 ` Junio C Hamano
2015-11-30 19:00 ` Mike Crowe [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151130190021.GA29232@mcrowe.com \
--to=mac@mcrowe.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).