Re: What's cooking in git.git (May 2017, #01; Mon, 1)

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: May 1, 2017, 17:44 UTC
Message-ID: <CACBZZX6FfLEQGaCWj=vsMrOsPwKSEc2uW+bXDu4e3rhe18_VaQ@mail.gmail.com>
In-Reply-To: <20170501162132.GA39135@google.com>

On Mon, May 1, 2017 at 6:21 PM, Brandon Williams <bmwill@google.com> wrote:

Show 23 quoted lines

> On 05/01, Ęvar Arnfjörš Bjarmason wrote:
>> On Mon, May 1, 2017 at 7:35 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> > * ab/clone-no-tags (2017-05-01) 3 commits
>> >   (merged to 'next' on 2017-04-30 at 601649896a)
>> >  + tests: rename a test having to do with shallow submodules
>> >  + clone: add a --no-tags option to clone without tags
>> >  + tests: change "cd ... && git fetch" to "cd &&\n\tgit fetch"
>> >
>> >  "git clone" learned the "--no-tags" option not to fetch all tags
>> >  initially, and also set up the tagopt not to follow any tags in
>> >  subsequent fetches.
>> >
>> >  Will cook in 'next'.
>>
>> Thanks for trimming off the top 2 patches. I've dropped those myself,
>> if someone (Brandon || Stefan) more interested in working on
>> submodules wants to pick them up that would be neat, but I don't need
>> it myself & doing it differently than the existing submodule options
>> would take too much of my time.
>
> Yeah we can add it to our backlog, though I'm not sure how quickly we'll
> be able to get to it.  If you end up needing this sooner just let me
> know.

I don't need it at all, I just thought it was prudent to add the submodule part of passing clone options / config when adding a new option since there were some existing options that did that.

Since there's outstanding debate about the interface for that sort of thing I'll just leave that to people who care more about submodules if they'd like to pursue it.