Stefan Haller writes: >Gelonida N <gelonida@xxxxxxxxx> wrote: > >> What is the best way to fastforward all fastforwardable tracking >> branches after a git fetch? > > Here's a script that does this. It isn't very well tested, I hope I > didn't miss any edge cases. Use at your own risk. Local branches can track each other. So the script needs to toposort the branches, or to loop until either nothing was done or an error happened. (The latter to prevent an eternal loop on error.) I've wished for a more limited 'git ff' command than this: - git update-ref --ff-only, and branch/fetch options based on this. - Fast-forward only the branches tracking one particular remote/branch, and maybe branches tracking the fast-forwarded branches. - Fast-forward to another remote or branch than the tracked one. I have a few aliases for it, but never thought much of a good common design. -- Hallvard -- 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