[arch-projects] [netctl] [GIT] Network control utility based on systemd branch master updated. 1.16-5-g4be6904

2018-06-26 Thread Jouke Witteveen via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Network control utility based on systemd". The branch, master has been updated via 4be6904e2518b5b13675439d6b89592e6bb4a6e3

[arch-projects] [netctl] [GIT] Network control utility based on systemd annotated tag 1.17 created. 1.17

2018-06-26 Thread Jouke Witteveen via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Network control utility based on systemd". The annotated tag, 1.17 has been created at 00116412c1b163ba2fe4b5ae6c77e4b09dcc68f0

Re: [arch-projects] [netctl] [PATCH] wifi-menu: Support UTF-8 encoded SSIDs (FS#45384)

2018-06-26 Thread Emil Velikov via arch-projects
Hi Jouke, Thanks for fixing this! Sharing a couple of ideas that come to mind. On 23 June 2018 at 12:25, Jouke Witteveen via arch-projects wrote: > Strictly speaking, we should check with the SSIDEncoding value sent out > by the station, as specified in the 2012 version of 802.11 (page 566), >

[arch-projects] [netctl] [PATCH] Simplify init_profiles() implementation

2018-06-26 Thread Emil Velikov via arch-projects
From: Emil Velikov Currently each profile is handles in two stages: - a unique value is returned for a set of patterns matches - depending on the value the profile/essid is added to global lists A shorter and simpler solution is to omit the unnecessary value passing/processing all together.

Re: [arch-projects] [netctl] [PATCH] wifi-menu: Support UTF-8 encoded SSIDs (FS#45384)

2018-06-26 Thread Emil Velikov via arch-projects
On 26 June 2018 at 11:34, Jouke Witteveen wrote: > On Tue, Jun 26, 2018 at 12:17 PM Emil Velikov > wrote: >> On 23 June 2018 at 12:25, Jouke Witteveen via arch-projects >> wrote: >> > Strictly speaking, we should check with the SSIDEncoding value sent out >> > by the station, as specified in