2018-11-09 10:05:04 +0000 | commented answer | Should we migrate development to GitLab? => Right, I forgot about that. That's feature I really miss. You can configure gitlab MR to accept FF merges only. |
2018-11-07 14:08:12 +0000 | commented answer | Should we migrate development to GitLab? I'd go with GITLAB. Pros: UI much more attractive, intuitive and versatile compared to gerrit workflow similar to git |
2018-11-07 13:30:12 +0000 | received badge | ● Rapid Responder (source) |
2018-11-07 13:30:12 +0000 | answered a question | Should we migrate development to GitLab? I'd go with GITLAB. Pros: UI much more attractive, intuitive and versatile compared to gerrit workflow similar to git |
2017-11-07 21:40:24 +0000 | received badge | ● Rapid Responder (source) |
2017-11-07 21:40:24 +0000 | answered a question | Why is wireshark non responsive? Try to capture with a fresh profile. That can be related to some options you have set. |
2017-11-07 11:45:16 +0000 | received badge | ● Editor (source) |
2017-11-07 11:45:16 +0000 | edited answer | How to get random packets from a .pcap file? tshark should do the job tshark -Y "frame.number => 10000 and frame.number <= 150000" -r capture.pcap -w capture |
2017-11-07 11:35:30 +0000 | answered a question | How to get random packets from a .pcap file? tshark should do the job tshark -Y "frame.number => 10000 and frame.number <= 150000" -r capture.pcap -w capture |
2017-11-07 10:17:03 +0000 | answered a question | newbe tried to start wireshark and get the message: "(wireshark:30765): Gtk-WARNING **: cannot open display:" You have some options for capturing: 1) using wireshark on debian (like you did). To do this, you need to install xauth |