arehbein has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/30134 ) Change subject: WIP: ttcn3-dumpcap*.sh: Don't use lsof ...................................................................... Patch Set 1: (1 comment) Patchset: PS1: I haven't yet read anything about how WIP-branches are to be used here. As indicated by my previous question in the 'sob'-chat, I was looking for a way to be able to have 'docker-playground' point at my changes so I can have them tested - for me that's quicker and easier right now than manually setting up tests. So, to be clear, for me this branch is just a 'WIP'-remote that I can have my branch of 'docker-playground' point to in order to see if my changes are breaking anything or not by running 'jenkins.sh' locally on my 'docker-playground' branch. I didn't see any other way of having my changes appear in the remote repo for fetching back to my local repo except for submitting them on Gerrit - the idea being that as long as it stays in my WIP-branch, it doesn't matter. If that is not acceptable, please tell me where I can push such WIP changes that I want to try out, and I'd be curious to know what other devs use their WIP branches for (or point me to a Wiki page, I guess... I did read around in the Wikis but don't recall reading about WIP branches)/how they make WIP commits appear in their remote for fetching without submitting them. I'm not yet aware where else I could/should push such changes. Edit: I wrote this earlier, but I still have to get used to the the draft-feature for replies so here goes a late reply. I think next time I'll try the private branch feature of Gerrit (I think appending a %private), if our server supports it. -- To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/30134 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-ttcn3-hacks Gerrit-Branch: arehbein/wip Gerrit-Change-Id: Ie34eaa778f78b9685dd601d5e9898829caf0c7ca Gerrit-Change-Number: 30134 Gerrit-PatchSet: 1 Gerrit-Owner: arehbein <arehbein(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: arehbein <arehbein(a)sysmocom.de> Gerrit-CC: pespin <pespin(a)sysmocom.de> Gerrit-Comment-Date: Thu, 17 Nov 2022 19:31:10 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: pespin <pespin(a)sysmocom.de> Gerrit-MessageType: comment