The --skipfirst option to emerge is only recognized if --resume is also specified, so --skipfirst should imply --resume.
That would be great. Lots of times I'm trying to type "emerge --resume --skipfirst" while emerge is spurting output, so I can't see if I made any typos. If the man pages said "--skipfirst implies --resume", then I'd know I could just type emerge --skipfirst, which is less error prone. I usually don't find out I made a typo for a few days, and that is sure annoying, since it causes a few days' delay more. This is usually useful to me during preemtive skipfirst resume command buffering for any failures. About 50% of the time there's some failure someplace that I have to resolve, and I don't have time to resolve every single one each time I do an upgrade, or else the systems would never be current. I've often wondered if there is an autoskipping mode in emerge. So, if there isn't, I'll add to the above very sensible and rather simple enhancement request a more complex enhancement request like --autoskipresume which would continue to the next ebuild after any failure (i.e., not quit). Come to think of it, that's not so complex: just don't exit from emerging when there's an error -- instead, skip to next ebuild. This is useful even in systems with very little ~x86 sprinkled in /etc/portage/package.keywords, although I know those who have more ~ would be even more grateful.
Fixed.
Released in 2.1_pre2.
