Ok, so this has been done for both the master and autotools-conversion
branches.
If you already have these checked out somewhere, you may run into an
issue with 'git pull' related to it not wanting to overwrite existing
files in the ksh93 hierarchy.
To fix it, simply run 'rm -rf
I agree; submodules are a hassle and always seem to go wrong for me somehow.
I’d rather see it in-tree.
-- Matthew R. Trower
> On Jun 21, 2021, at 18:16, Christopher Turkel
> wrote:
>
> Go for it!
>
> Sent from my iPhone
>
>> On Jun 21, 2021, at 6:19 PM, Jon Trulson wrote:
>>
>> Hi,
Go for it!
Sent from my iPhone
> On Jun 21, 2021, at 6:19 PM, Jon Trulson wrote:
>
> Hi,
>
> I'd like to switch ksh93 from being a submodule to a subtree. With a
> subtree, all of the code is present, which means there is no need to use
> --recursive when cloning, or 'submodule update
On Mon, 21 Jun 2021 at 23:18, Jon Trulson wrote:
> I'd like to switch ksh93 from being a submodule to a subtree. With a
> subtree, all of the code is present, which means there is no need to use
> --recursive when cloning, or 'submodule update --init' when updating.
>
> It seems many people
Hi,
I'd like to switch ksh93 from being a submodule to a subtree. With a
subtree, all of the code is present, which means there is no need to use
--recursive when cloning, or 'submodule update --init' when updating.
It seems many people think submodules are a problem, and I think the
extra
