2018-03-08 10:40 GMT+01:00 Ian Campbell <ijc@xxxxxxxxxxxxxx>: > > On Thu, 2018-03-08 at 10:25 +0100, Ævar Arnfjörð Bjarmason wrote: > > > > The first filter-branch call required 7168 steps, so did the second call... > > > I also tried without the --prune option of remote update (I had to add > > > --force to the second filter-branch), but nothing changed. > > You can see an example of the usage in: > https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git/ > > in the `scripts/` sub dir (flow is `cronjob` → `filter.sh` → `git > filter-branch...`. > > I think the big difference is rather than `--all` you need to give it > the `previous..now` range since that is the update you wish to do > (first time around you just give it `now`). > > The devicetree-rebasing scripting arranges that by keeping the previous > in a separate branch. > > Ian. Thank you for your quick reply, Ian. Just a couple of questions: 1. it seems to me it's not possible to process all the branches in one go. Am I right? 2. Why do you have this line in filter.sh? `rm -f .git/refs/original/refs/heads/${UPSTREAM_REWRITTEN}` Thank you again, Michele
