Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: >> 5. Adding something like git-fetch --all to allow it to pick up all new >> branches > > IIRC this idea was rejected, but I would find it useful. Especially with > what Han-Wen said: you can store the branches you fetch with "git fetch > --all <nick>" under .git/refs/remotes/<nick>/<branchname>. With separate-remote layout, this can be done without risk of tracking refname clashing with local refname, which was the primary reason for an earlier reluctance. While separate-remote layout also solves Carl's "do not want to track tracking branches remote has" problem, local branch namespace can have both for-others (not necessarily "public" but could be "for colleagues") and throwaway branches, so --all is probably not the right thing to do in most cases. But I am Ok with the approach of seeing how well it works out in practice by doing the simplest "--all" and giving options to restrict it later. - 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