• 17 Posts
  • 2.04K Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle













  • yeah, I think these are the main hurdles for me:

    1. Untracked files are not copied

    When you create a new worktree, it is created from whatever is comitted, so gitignored or uncomitted files are not copied.

    So if you have .env files, you have to copy them over manually. And for dependencies, like for example node_modules, you would have to run npm install again in the new worktree.

    Mainly .env files, as they are handcrafted. And:

    1. Editor / IDE complexity.

    A few projects I work on are multi-root (using VS Code terminology) and that’s already complex enough. Adding worktree directories means adding a level to that, which I’m not bought in. And I don’t want a separate workspace for each branch I work on, that just shifts the complexity from git to the IDE / editor.



  • Eager Eagle@lemmy.worldtoLinux@lemmy.mlHow bad is my partitioning?
    link
    fedilink
    English
    arrow-up
    57
    ·
    edit-2
    5 days ago

    I think the partitioning itself is fine, but I wouldn’t have 3 operating systems on a 256 GB NVMe, because I’d be running out of space a lot.

    if you won’t ever use Windows, you can nuke it. Then I’d consider making one of the Linux ones a VM - if you’re trying out that distro. That will cut down 12 partitions to 5.

    Lastly, you can look into btrfs to make better use of space between (the current) p11 and p12: you can make them subvolumes that won’t eat up each other’s storage when not in use.