4 ms·

> "git rebase" learned to interpret a lone "-" as "@{-1}", the branch that we were previously on. Cool, I was just looking for something like this with "git me

> "git rebase" learned to interpret a lone "-" as "@{-1}", the branch that we were previously on. Cool, I was just looking for something like this with "git merge". Turns out "git merge" already supports it, and I need to get better at using the reflog (@{...}). > "git add <path>" is the same as "git add -A <path>" now. > The "-q" option to "git diff-files", which does NOT mean "quiet", has been removed More intuitive. > The bitmap-index feature from JGit has been ported, which should significantly improve performance when serving objects from a repository that uses it. Improves clone performance if you're pulling lots of history, but there still doesn't seem to be a way to sparse-checkout without fetching the entire .git repo.

wfn 12y ago
> but there still doesn't seem to be a way to sparse-checkout without fetching the entire .git repo. I'm not entirely sure if this is what you want, but sparse-checkouting only parts of the repo is possible: http://jasonkarns.com/blog/subdirectory-checkouts-with-git-sparse-checkout/ http://jasonkarns.com/blog/subdirectory-checkouts-with-git-s... For cloning a particular branch, there's also (since 1.7.10) git clone -b your_branch_name --single-branch git://some.remote/repo.git
jackyb 12y ago
Use "git clone --depth [depth] [remote-url]"?
- justinmk 12y ago
  Even with depth=1 it still pulls the .git/ blobs for the entire repo. The use case is: only want a subdirectory, and only want the repo/history objects for that subdirectory.