Hallvard B Furuseth <h.b.furuseth@xxxxxxxxxxx> wrote: > 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.) Is this just theoretical, or are there real use cases for this? What would be a workflow with such a local tracking branch? For me personally, the script is good enough, because I only ever have branches that track an 'origin' branch with the same name. -- Stefan Haller Berlin, Germany http://www.haller-berlin.de/ -- 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