Hi Martin, On Sun, Jan 27, 2019, 17:37 Martin Pitt <mp...@debian.org wrote:
> Hello Felipe, > > Felipe Sateler [2019-01-26 0:04 +0000]: > > Bug #919390 in systemd reported by you has been fixed in the > > Git repository and is awaiting an upload. You can see the commit > > message below and you can check the diff of the fix at: > > > > > https://salsa.debian.org/systemd-team/systemd/commit/ca9bf5fdd69e1f6bb137d905f90225de7fc057e4 > > > > ------------------------------------------------------------------------ > > Pick patch proposed upstream to reduce journald memory usage > > > > Closes: #919390 > > This should have been #920018. I was about to do the cherry-picks, but I'm > really confused here. Where *did* your two commits land? They are clearly > not > on master, and there are no other (recent) branches. Even trying to show > the > SHA directly doesn't work (no such object). > > Did you force-unpush them? Or was this an unnamed branch somehow? Should I > pick > them from the salsa web UI and push them to master (and fixing the bug > number > while I'm at it), and upload? > I picked the patches, but before I uploaded I had to leave. I also accidentally pushed those picks to the wrong branch (adding salsa CI integration), and then unpushed them. I am not on my pc now so if you can upload the fixes that would be cool. Sorry about the confusion. We should probably restrict the notification hook to themaster branch. Saludos, Felipe Sateler
