Bernie: I feel like this is something you'd have access to do and that you'd understand if there could possibly be any weird build system implications here.

Basically the suggestion here is to just rename cros/master to something else at:

  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/master

...maybe rename "master" to "chromeos-2.6.32"

For firmware:

  https://chromium.googlesource.com/chromiumos/third_party/coreboot/+/master

Maybe you'd rename it to "old" or something?

---

If you're busy or you think someone else would be better suited, please yell.

+Stefan and Patrick FYI, but I'm pretty sure cros/master is some old outdated branch that nobody needs anymore in coreboot and we should get rid of it (or rename it to something nobody would care about) to avoid confusing people.

coreboot's master should be renamed to something else, yes.

Probably not deleted since I don't know if those commits are still used in some ancient branch (if any they would have been branched pre-2013.04, nearly 5 years ago, and we probably didn't use coreboot back then but u-boot or Insyde)

Yeah, move not delete is right IMHO.  About the worst I can think of that would happen here is that if someone syncs to a manifest from 5 years ago that it would have trouble syncing because the old manifest would still say to sync down "master".  Of course if you could convince the sync to pass, the build would still be OK because the ebuilds would specify a certain git hash.

Luckily, though, all release branches should be fine since we create a new branch for each release.

Permission to do that seems to be limited to https://ganpati.corp.google.com/#Group_Info?name=chromeos-branch-creators@prod.google.com

Bernie, could you please rename master on chromiumos/third_party/coreboot?
The new name doesn't matter as long as it stays out of the way. I'd propose chromeos-2012 (which should be a reasonable approximation) to give it some context.