| Subject | English | Russian |
| Игорь Миг | baseless accusations | бездоказательные обвинения |
| formal | baseless accusations | беспочвенные обвинения (ART Vancouver) |
| Игорь Миг | baseless accusations | огульные обвинения |
| Игорь Миг | baseless accusations | голословные обвинения |
| crim.law. | baseless accusations which are not backed up by any evidence | голословные обвинения, не подкреплённые никакими доказательствами (Alex_Odeychuk) |
| crim.law. | baseless allegation | необоснованное обвинение (Alex_Odeychuk) |
| crim.law. | baseless allegation | беспочвенное обвинение (Alex_Odeychuk) |
| law | baseless allegation | безосновательное заявление (Thomson Reuters; контекстуальный перевод Alex_Odeychuk) |
| polit. | baseless argument | безосновательный аргумент |
| polit. | baseless argument | аргумент, лишённый основания |
| busin. | baseless assertion | необоснованное утверждение |
| tech. | baseless bulb | бесцокольный баллон |
| patents. | baseless charge | необоснованное обвинение |
| police | baseless claim | беспочвенное обвинение (Val_Ships) |
| Gruzovik | baseless fear | напрасная тревога |
| Makarov. | baseless fears | необоснованные страхи |
| Makarov. | baseless gossip | необоснованные сплетни |
| progr. | baseless merge | слияние без базовой версии (Alex_Odeychuk) |
| progr. | baseless merge | слияние без основы (A baseless merge is a merging of two arbitrary branches in version control without reference to a base version. This is sometimes necessary if the source code was originally imported in a flat structure without the branch relationship being in place, or if you want to merge between one branch and another that is not a direct parent or child. Because no base version is being used to compare against, the probability of the server detecting conflicts occurring between the two branches is much higher. For example, if a file is renamed in one branch and edited in the other, it shows up as a file delete conflicting with the file edit, and then a file add that gives no hint as to which file it is related to, or that there is an edit intended for this file in the other branch. For this reason, baseless merges are discouraged. Your branching model should attempt to constrain most merges between parent and child branches to minimize the amount of baseless merging required. Alex_Odeychuk) |
| progr. | baseless merging | выполнение слияния без основы (A baseless merge is a merging of two arbitrary branches in version control without reference to a base version. This is sometimes necessary if the source code was originally imported in a flat structure without the branch relationship being in place, or if you want to merge between one branch and another that is not a direct parent or child. Because no base version is being used to compare against, the probability of the server detecting conflicts occurring between the two branches is much higher. For example, if a file is renamed in one branch and edited in the other, it shows up as a file delete conflicting with the file edit, and then a file add that gives no hint as to which file it is related to, or that there is an edit intended for this file in the other branch. For this reason, baseless merges are discouraged. Your branching model should attempt to constrain most merges between parent and child branches to minimize the amount of baseless merging required. Alex_Odeychuk) |
| patents. | baseless opposition | необоснованное возражение |
| adv. | baseless opposition | необоснованное противодействие |
| PR | baseless rumors | безосновательные слухи (defense.gov Alex_Odeychuk) |
| Makarov. | baseless rumours | необоснованные слухи |
| gen. | baseless scare | беспричинный страх |
| gen. | baseless statement | необоснованное утверждение |
| tech. | baseless tube | бесцокольная лампа |
| law | legally baseless | не имеющий предусмотренных законом оснований (CNN Alex_Odeychuk) |
| progr. | the amount of baseless merging | масштаб слияния без основы (A baseless merge is a merging of two arbitrary branches in version control without reference to a base version. This is sometimes necessary if the source code was originally imported in a flat structure without the branch relationship being in place, or if you want to merge between one branch and another that is not a direct parent or child. Because no base version is being used to compare against, the probability of the server detecting conflicts occurring between the two branches is much higher. For example, if a file is renamed in one branch and edited in the other, it shows up as a file delete conflicting with the file edit, and then a file add that gives no hint as to which file it is related to, or that there is an edit intended for this file in the other branch. For this reason, baseless merges are discouraged. Your branching model should attempt to constrain most merges between parent and child branches to minimize the amount of baseless merging required. Alex_Odeychuk) |
| gen. | the charge is completely baseless | это обвинение ни на чём не основано |