Junio C Hamano <gitster@xxxxxxxxx> writes: > Hmph, this is interesting. > > "git rebase" does take "--rerere-autoupdate" option from the command > line, and propagates it to a later invocation of "rebase --continue" > by storing the value to $state_dir/allow_rerere_autoupdate file and > reading the value from it. $allow_rerere_autoupdate shell variable > is used to hold the setting. > > I'd expect that this variable to be used in invocations of "git am" > in git-rebase--am.sh; but that does not seem to be the case. I > wonder if this was once working but over time we broke the feature > without anybody noticing it, or if the support was added but not > completed and the feature was a no-op from the beginning? At least in v1.7.0 when doing "rebase -m", the rerere-autoupdate was plumbed correctly through to the invocation of "git merge" that is done inside git-rebase.sh. I do not see the same option passed down to the invocation of "git am", so perhaps nobody cared back then about rerere during "git rebase" that does not use "git am" backend, even though "git am" itself were capable of talking the option. In any case, if you corrected the existing "git rebase" and its backend so that "--rerere-autoupdate" works as advertised, I think you are already 80% there without adding a yet another option, as I suspect that the most of the need for avoiding "git add" during a "git rebase" session is during a conflict resolution, and allowing "rerere" to automatically update the index with auto-resolution will leave _only_ changes to the paths the end user actually needs to take a look and manually fix still not in the index. And from the workflow point of view, encouraging them to "git add" their manual resolution after they are satisified with their changes by not doing "git add" blindly for all changes, like your --autostage" does, is probably a good thing.
