From: Antonio Ospite <ao2@ao2.it>
To: Stefan Beller <sbeller@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] builtin/grep.c: remote superflous submodule code
Date: Sat, 6 Oct 2018 10:59:59 +0200 [thread overview]
Message-ID: <20181006105959.47f8ccf38281d8bdd07448e7@ao2.it> (raw)
In-Reply-To: <20181005224557.31420-1-sbeller@google.com>
On Fri, 5 Oct 2018 15:45:57 -0700
Stefan Beller <sbeller@google.com> wrote:
> In f9ee2fcdfa (grep: recurse in-process using 'struct repository',
> 2017-08-02), we introduced a call to repo_read_gitmodules in builtin/grep
> to simplify the submodule handling.
>
> After ff6f1f564c4 (submodule-config: lazy-load a repository's .gitmodules
> file, 2017-08-03) this is no longer necessary, but that commit did not
> cleanup the whole tree, but just show cased the new way how to deal with
> submodules in ls-files.
>
> Cleanup the only remaining caller to repo_read_gitmodules outside of
> submodule.c
>
> Signed-off-by: Stefan Beller <sbeller@google.com>
Not sure if I am entitled to formally ack it, but:
Acked-by: Antonio Ospite <ao2@ao2.it>
> ---
>
> Antonio Ospite writes:
> > BTW, with Stefan Beller we also identified some unneeded code which
> > could have been removed to alleviate the issue, but that would not have
> > solved it completely; so, I am not removing the unnecessary call to
> > repo_read_gitmodules() builtin/grep.c in this series, possibly this can
> > become a stand-alone change.
>
> Here is the stand-alone change.
>
Thank you for sending it.
Ciao,
Antonio
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
next prev parent reply other threads:[~2018-10-06 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 22:45 [PATCH] builtin/grep.c: remote superflous submodule code Stefan Beller
2018-10-06 8:59 ` Antonio Ospite [this message]
2018-10-07 0:29 ` Junio C Hamano
2018-10-07 0:33 ` Junio C Hamano
2018-10-09 0:14 ` Stefan Beller
-- strict thread matches above, loose matches on Subject: below --
2018-10-09 18:35 Stefan Beller
2018-10-10 0:10 ` Jonathan Tan
2018-10-10 22:49 ` Stefan Beller
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=20181006105959.47f8ccf38281d8bdd07448e7@ao2.it \
--to=ao2@ao2.it \
--cc=git@vger.kernel.org \
--cc=sbeller@google.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.
Code repositories for project(s) associated with this public 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).