264
Can't get closed as duplicate if nobody can find the duplicates (thelemmy.club)
submitted 2 days ago* by to c/programmer_humor@programming.dev
27 comments fedilink hide all child comments
 

I swear someones just using it as a harder drive at this point

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 day ago (3 children)

Isn't that part of the problem described in the article? A shallow clone? Github has trouble with exactly that.

Maybe it's time the community stepped in an provided alternative solutions to nixpkgs. We can talk about them here, but in the end somebody has to implement them.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 1 day ago* (2 children)

    no shallow is --shallow. the difference is --depth refers to the history (as reported by, e.g. git log), whereas shallow will only check out the root of the repository and any paths explicitly specified. i guess the article is describing some sort of problem with users who convert their shallow repository to a regular full repo. i wouldn't know a lot about that.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 17 hours ago (1 child)

    This is the documentation from git clone --help

    --depth=<depth>

    Create a shallow clone with a history truncated to the specified number of commits. Implies --single-branch unless --no-single-branch is given to fetch the histories near the tips of all branches. If you want to clone submodules shallowly, also pass --shallow-submodules.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •