On OSX `wc` prefixes the output of numbers with whitespace, such that
the `commit_count` would be "SP ". When using that in
git submodule update --init --depth=$commit_count
the depth would be empty and the number is interpreted as the pathspec.
Fix this by not using `wc` and rather instruct
Stefan Beller writes:
> On Wed, Aug 10, 2016 at 11:27 AM, Junio C Hamano wrote:
>> Stefan Beller writes:
>>
>>> On OSX `wc` prefixes the output of numbers with whitespace, such that
>>> the `commit_count` would be "SP ". When using that in
>>>
>>> git submodule update --init --depth=$commit
> On 10 Aug 2016, at 19:56, Stefan Beller wrote:
>
> On OSX `wc` prefixes the output of numbers with whitespace, such that
> the `commit_count` would be "SP ". When using that in
>
>git submodule update --init --depth=$commit_count
>
> the depth would be empty and the number is interpreted
On Wed, Aug 10, 2016 at 11:27 AM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> On OSX `wc` prefixes the output of numbers with whitespace, such that
>> the `commit_count` would be "SP ". When using that in
>>
>> git submodule update --init --depth=$commit_count
>>
>> the depth would be
Stefan Beller writes:
> On OSX `wc` prefixes the output of numbers with whitespace, such that
> the `commit_count` would be "SP ". When using that in
>
> git submodule update --init --depth=$commit_count
>
> the depth would be empty and the number is interpreted as the pathspec.
> Fix this by
5 matches
Mail list logo