Francis Moreau <francis.moro@xxxxxxxxx> writes: > When rebasing my current branch onto the last master one, there're > sometimes some commits which doesn't add anything anymore. > > Currently git-rebase produces the following message: > > nothing added to commit but untracked files present (use "git add" to track) > > Would it be possible to add a new option to this command so it simply > skip the unneeded commit ? Our assumption has always been that it is a notable event that a patch that does not get filtered with internal "git cherry" (which culls patches that are textually identical to those that are already merged to the history you are rebasing onto) becomes totally unneeded and is safe to ask for human confirmation in the form of "rebase --skip" than to ignore it and give potentially incorrect result silently. Obviously you do not find it a notable event for some reason. We would need to understand why, and if the reason is sensible, it _might_ make sense to allow a user to say "git rebase --ignore-merged" or something when starting the rebase. -- 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