search

jedbrown / git-fat

Simple way to handle fat files without committing them to git, supports synchronization using rsync
BSD 2-Clause "Simplified" License
621 stars 137 forks source link

Update information in Readme. #47

Closed Xender closed 10 years ago

Xender commented 10 years ago

Shallow clones ARE (I think) fully functional in non-acient git versions.

Manpage says that you can push/pull to/from a shallow clone. You can also make further clones of it.

Are there another limitations of shallow clones which hasn't been lifted in newer Git versions?

jedbrown commented 10 years ago

It's true that recent versions of Git allow this, but it's still easy to get clones that don't have sufficient history, and it's difficult to deepen a clone without getting more than you want (because the distance-n front of the DAG often sends you way back in the history due to merges of short branches). I don't mind merging this branch, but the issue is still nuanced and I don't think the current version is wrong either.

Xender commented 10 years ago

How you'd reword it then?

Well, it's true that shallow clones has their shortcomings. I don't also want to depreciate git-fat in any way.

The issue is that you can still find people who don't know that a lot of shallows clones' limitations don't apply in newer Git versions, so if it's feasible, it'd be nice to help stopping this misinformation.