This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
osmith gerrit-no-reply at lists.osmocom.orgosmith has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ci/+/18444 ) Change subject: OBS: next: osmo-trx: use branch osmith/ipc ...................................................................... Patch Set 2: > Patch Set 2: > > this works for now. Maybe we should simply introduce some automatic mechanism where the "next" builds will use a "next" branch in every repository, or fall back to "master" if there is no "next" branch? This way, all a developer has to do to make a change visible in "next" is to push it there and wait for the OBS rebuild (or manually trigger it via jenkins web interface")? Done in https://gerrit.osmocom.org/c/osmo-ci/+/18442 -- To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/18444 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-ci Gerrit-Branch: master Gerrit-Change-Id: If35ccddf72a6ce835dc29deea45def7a790e85a7 Gerrit-Change-Number: 18444 Gerrit-PatchSet: 2 Gerrit-Owner: osmith <osmith at sysmocom.de> Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-Reviewer: pespin <pespin at sysmocom.de> Gerrit-Comment-Date: Thu, 28 May 2020 08:00:47 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: No Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20200528/c2730208/attachment.htm>