From: Junio C Hamano <gitster@pobox.com>
To: Brandon Williams <bmwill@google.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2017, #10; Fri, 24)
Date: Sun, 26 Mar 2017 16:02:27 -0700 [thread overview]
Message-ID: <xmqqo9wn4p6k.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170324235357.GA26537@google.com> (Brandon Williams's message of "Fri, 24 Mar 2017 16:53:57 -0700")
Brandon Williams <bmwill@google.com> writes:
> On 03/24, Junio C Hamano wrote:
>> * bw/recurse-submodules-relative-fix (2017-03-17) 5 commits
>> - ls-files: fix bug when recursing with relative pathspec
>> - ls-files: fix typo in variable name
>> - grep: fix bug when recursing with relative pathspec
>> - setup: allow for prefix to be passed to git commands
>> - grep: fix help text typo
>>
>> A few commands that recently learned the "--recurse-submodule"
>> option misbehaved when started from a subdirectory of the
>> superproject.
>
> Anything more you think needs to be done about this? I noticed that
> Dscho's config series hit master so I could rebase against that (as
> there is a small conflict). Aside from that it didn't seem like there
> were many complaints with the proposed fix.
I saw no particular issues myself. Do others find this series good
(not just "meh--it is harmless" but I want to hear a positive "yes
these are good changes")?
prev parent reply other threads:[~2017-03-26 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 21:21 What's cooking in git.git (Mar 2017, #10; Fri, 24) Junio C Hamano
2017-03-24 23:26 ` Ævar Arnfjörð Bjarmason
2017-03-24 23:53 ` Brandon Williams
2017-03-26 23:02 ` Junio C Hamano [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
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=xmqqo9wn4p6k.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
/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).