Re: got(1) in base consideration

Hi Kyle,

> I've been toying around with the idea of pulling got(1) into base (...)
> not supporting it for general usage. 
> The idea would instead be (...) to do the bare minimum to functionally maintain a local copy 
> of our git repos.

I think that can have value for server/small installs where the source is still needed (package building, local tweaks, etc.).

> (rest)

I've never used 'got' so far, but is it impossible to just checkout the bare repository without creating any worktrees?  That could be a useful "option" for people that know they will install and use 'git' afterwards, and solves the problem of trying to avoid losing uncommitted work by just making it disappear.

I guess that detecting uncommitted work with 'got' is as easy as with 'git'?  I personally would not be shocked if the script flat out refuses to proceed on uncommitted work, and see trying to automatically detect, backup and reinstall this work as some nice-to-have that can be receded into the indefinite future.

Thanks and regards.

-- 
Olivier Certner