On 12/1/08, Jeff King <peff@xxxxxxxx> wrote: > [..snip..] > > > Er, what? git-fetch takes a refspec very similar to the ones used by > git-push. The real reason that (2) is not an acceptable solution is that > you can't necessarily connect to the source repo (e.g., it is on your > workstation with no ssh or git server running). > > -Peff I am sorry, I had to be more accurate in my wording. "git fetch" with no explicit refspecs fetches everything in. It is quite cumbersome to form a refspec for git-fetch operation if you are not logged in into the "source repo" machine. git-fetch does not have a --dry-run option to help discover all the branch/tag names on the source side needed for a meaningful refspec. "git-push -v --dry-run" allows one to experiment and see what branches/tags exist at the destination and form refspecs selectively. To the best of my knowledge, git-fetch does not provide such discovery tools. --Leo-- -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
