Chromium 140.0.7339.127 (boo#1249388) #3
Reference in New Issue
Block a user
Delete Branch ":leap-16.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Chromium 140.0.7339.127 https://bugzilla.opensuse.org/show_bug.cgi?id=1249388
Legal review in progress.
I see
leap-16.0is already ahead offactorybranch here.In my fork? Certainly. In pool/chromium factory branch ... depends on how long the repo needs to catch up.
In any case this should match
openSUSE:Factory/chromiumwith SR#1303512 accepted.No, I meant the
leap-16.0branch of pool/chromium is ahead of thefactorybranch of the same repo. In other words:factoryis ate557e90812update to 139.0.7258.138leap-16.0is at 140.0.7339.80Or, stated in other terms,
factorybranch of pool/chromium is behind openSUSE:Factory/chromium 👎I think the general preference is to use commits from the
factorybranch also in theleap-16.0branch, as opposed to building up a parallel history.The parallel history is already built, because the factory branch did not keep up with what was actually in Factory. Additionally, this preference cannot apply universally, simply because not all packages will be maintained in Leap with Factory sources.
Legal review in progress.
Legal reviewed by lkocman as acceptable: