Re: Git haas gone wild (Rust)

On 2025-09-06 22:13, Warner Losh wrote:
> 
> 
> On Sat, Sep 6, 2025, 1:47 PM Daniel Engberg <diizzy@freebsd.org 
> <mailto:diizzy@freebsd.org>> wrote:
> 
>     __
>     On 2025-09-06 20:52, Warner Losh wrote:
>>
>>
>>     On Sat, Sep 6, 2025, 12:37 PM Kyle Evans <kevans@freebsd.org
>>     <mailto:kevans@freebsd.org>> wrote:
>>
>>         On 9/6/25 08:47, Warner Losh wrote:
>>         >
>>         >
>>         > On Sat, Sep 6, 2025, 7:39 AM Eugene Grosbein
>>         <eugen@grosbein.net <mailto:eugen@grosbein.net>
>>         <mailto:eugen@grosbein.net <mailto:eugen@grosbein.net>>> wrote:
>>         >
>>         >     06.09.2025 20:17, Matthias Andree wrote:
>>         >
>>         >      > Am 05.09.25 um 18:42 schrieb Michael Osipov:
>>         >      >> Folks,
>>         >      >>
>>         >      >> you might want to enjoy or discuss: https://
>>         lore.kernel.org/ <https://lore.kernel.org/> <https://
>>         lore.kernel.org/ <https://lore.kernel.org/>> git/20250904-b4-
>>         pks-rust-breaking-change-v1-0-3af1d25e0be9@pks.im/T/#t
>>         <http://20250904-b4-pks-rust-breaking-change-
>>         v1-0-3af1d25e0be9@pks.im/T/#t> <http://20250904-b4-pks-rust-
>>         breaking-change-v1-0-3af1d25e0be9@pks.im/T/#t
>>         <http://20250904-b4-pks-rust-breaking-change-
>>         v1-0-3af1d25e0be9@pks.im/T/#t>>
>>         >      >>
>>         >      >> Michael
>>         >      >
>>         >      > This poses a bootstrapping problem, (if we need Git
>>         to get the Rust build for ports... there's a chicken-and-egg
>>         problem)
>>         >
>>         >     Maybe it is time for us to bring net/gitup into base system.
>>         >     It's written in pure C and comes under BSD2CLAUSE license.
>>         >     Also, it matured over many years and runs just fine.
>>         >
>>         >     For the reference: https://github.com/johnmehr/gitup
>>         <https://github.com/johnmehr/gitup> <https://github.com/
>>         johnmehr/gitup <https://github.com/johnmehr/gitup>>
>>         >
>>         >
>>         >
>>         > Got is better supported and wouldn't be an instant burden.
>>         >
>>         > Warner
>>         >
>>         >
>>
>>         fuz@ and I discussed this a little bit yesterday, too.  I
>>         think it'd be fine to introduce got if we have
>>         a simple wrapper to checkout (and maybe update) a repository
>>         in a git-compatible way so that one could
>>         easily migrate between the two.  Something like: clone the
>>         repository to /usr/{src,ports}.git, checkout a
>>         worktree to /usr/{src,ports}, then add a git-style .git
>>         symlink to point back to the appropriate .git dir
>>         so that git recognizes it as a worktree.
>>
>>         git itself can create an identical layout with `git clone --
>>         separate-git-dir=/usr/src.git ...`
>>
>>
>>     Yea. It's the perfect lightweight thing that can "upgrade" to
>>     native git if need be.. plus upstream is more active, imho...
>>     these wrappers would ease the transition.
>>
>>     Warner
>>
>>         Thanks,
>>
>>         Kyle Evans
>>
>     Got was really slow last time I tested it (a while back), is that
>     fixed now?
>     https://projects.pyret.net/files/public/freebsd/git-tools.htm
>     <https://projects.pyret.net/files/public/freebsd/git-tools.htm>
> 
> Slow at what? Last time I played with it, it wasn't bad. Not as good as 
> native git, but not so much slower it annoyed me much...
> 
> Warner
> 
> 
>     Best regards,
>     Daniel
> 

Cloning, see link? :)

Best regards,
Daniel