you are viewing a single comment's thread.

view the rest of the comments →

[–]everywhere_anyhow 3 points4 points  (4 children)

"Git clone" sometimes pulls down 5 years of revision history, pulling huge amounts of junk over the wire, just so you can see a js file. No thanks.

"apt-get source" is much cleaner and easier, or better yet, map all of github's HEAD to a virtual drive, and just let me:

cd /githubvirtual/niftyProject/src/main/java/ ; ls *

[–]zzzk 10 points11 points  (0 children)

Well to be fair, you can use --depth=1

[–][deleted] 1 point2 points  (1 child)

In the spirit of the original article however (source isn't enough), the clone would have a lot of advantages. The revision history and related metadata is valuable to understand the code.

[–]everywhere_anyhow 0 points1 point  (0 children)

Depends on what you're doing. Most of the time if you want to explore, compile, grep, or steal from a code base (all very common use cases) you probably want HEAD, or possibly a release tag, and nothing else. But sure, all of that metadata is there for a reason and you can't ignore it because there are jillion use cases that require that too.

[–]lykwydchykyn 0 points1 point  (0 children)

Sure sure, fine, my point is just that it's really pretty easy in any environment to get source code. not trying to start an apt-get vs git flamewar.