From: Daniel Zaoui <jackdanielz@eyomi.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Matheus Tavares Bernardino <matheus.bernardino@usp.br>,
Brandon Williams <bwilliams.eng@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: Weird behavior with git grep --recurse-submodules
Date: Tue, 16 Jul 2019 21:10:12 +0300 [thread overview]
Message-ID: <20190716211012.226b7059@zen> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1907101313450.46@tvgsbejvaqbjf.bet>
Hi Matheus,
Thank you for your response.
I really hope the change Brandon made is not a project decision. At least, it does seem to me like a bug.
How do you recommend me to solve this issue? Is there some place where I can check if some bug ticket has been created on this matter? I didn't find anything in the mailing list archives about this.
BR
Daniel
On Wed, 10 Jul 2019 13:14:18 +0200 (CEST)
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> [cC:ing Brandon via his current email address, as per .mailmap]
>
>
> On Wed, 10 Jul 2019, Matheus Tavares Bernardino wrote:
>
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
next prev parent reply other threads:[~2019-07-16 18:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 8:14 Weird behavior with git grep --recurse-submodules Daniel Zaoui
2019-07-10 6:43 ` Matheus Tavares Bernardino
2019-07-10 11:14 ` Johannes Schindelin
2019-07-16 18:10 ` Daniel Zaoui [this message]
2019-07-29 20:27 ` Matheus Tavares Bernardino
2019-07-30 16:53 ` [GSoC][PATCH] grep: fix worktree case in submodules Matheus Tavares
2019-07-30 20:04 ` Junio C Hamano
2019-07-30 22:02 ` Christian Couder
2019-07-31 15:57 ` Junio C Hamano
2019-08-01 3:08 ` Matheus Tavares Bernardino
2019-07-30 23:40 ` Matheus Tavares Bernardino
2019-07-31 15:35 ` [GSoC][PATCH v2] " Matheus Tavares
2019-08-01 3:13 ` [GSoC][PATCH v3] " Matheus Tavares
2019-08-03 23:39 ` Weird behavior with git grep --recurse-submodules Brandon Williams
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=20190716211012.226b7059@zen \
--to=jackdanielz@eyomi.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=bwilliams.eng@gmail.com \
--cc=git@vger.kernel.org \
--cc=matheus.bernardino@usp.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.