Re: [Openvpn-devel] state of sitnl patchset ?
пн, 10 июн. 2019 г. в 02:11, Gert Doering : > Hi, > > On Mon, Jun 10, 2019 at 02:06:47AM +0500, ?? wrote: > > > On Mon, Jun 10, 2019 at 12:05:52AM +0500, ?? > wrote: > > > > https://patchwork.openvpn.net/project/openvpn2/list/?series=428 says > > > "new" > > > > however, I see patchset is applied (and travis-ci is somewhat broken) > > > > > > > > are all paches applied already ? > > > > > > Patch status is communicated via the list - and my comments can be > > > nicely seen when clicking on each individual patch. > > > > it is complicated to view every patch and it's comments. > > is there a way to change status to "applied" on patchwork ? > > I'm leaving them in their current state as a reminder that there is > more work to do - clean up the code where needed, fix the regression > in 5/7, fix the buildslave blowup in 7/7. > thank you, that's I wanted to hear. "patches are still New, because it is not finished yet" > > (5/7 is actually fine in itself, the problem is an earlier patch which > already got applied, but where the code was never activated - so when > that code is fixed, 5/7 could be applied "as is". OTOH there are code > warts in 5/7, so maybe a v4 will come) > > gert > > -- > "If was one thing all people took for granted, was conviction that if you > feed honest figures into a computer, honest figures come out. Never > doubted > it myself till I met a computer with a sense of humor." > Robert A. Heinlein, The Moon is a Harsh > Mistress > > Gert Doering - Munich, Germany > g...@greenie.muc.de > ___ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
Re: [Openvpn-devel] state of sitnl patchset ?
Hi, On Mon, Jun 10, 2019 at 02:06:47AM +0500, ?? wrote: > > On Mon, Jun 10, 2019 at 12:05:52AM +0500, ?? wrote: > > > https://patchwork.openvpn.net/project/openvpn2/list/?series=428 says > > "new" > > > however, I see patchset is applied (and travis-ci is somewhat broken) > > > > > > are all paches applied already ? > > > > Patch status is communicated via the list - and my comments can be > > nicely seen when clicking on each individual patch. > > it is complicated to view every patch and it's comments. > is there a way to change status to "applied" on patchwork ? I'm leaving them in their current state as a reminder that there is more work to do - clean up the code where needed, fix the regression in 5/7, fix the buildslave blowup in 7/7. (5/7 is actually fine in itself, the problem is an earlier patch which already got applied, but where the code was never activated - so when that code is fixed, 5/7 could be applied "as is". OTOH there are code warts in 5/7, so maybe a v4 will come) gert -- "If was one thing all people took for granted, was conviction that if you feed honest figures into a computer, honest figures come out. Never doubted it myself till I met a computer with a sense of humor." Robert A. Heinlein, The Moon is a Harsh Mistress Gert Doering - Munich, Germany g...@greenie.muc.de signature.asc Description: PGP signature ___ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
Re: [Openvpn-devel] state of sitnl patchset ?
пн, 10 июн. 2019 г. в 01:37, Gert Doering : > Hi, > > On Mon, Jun 10, 2019 at 12:05:52AM +0500, ?? wrote: > > https://patchwork.openvpn.net/project/openvpn2/list/?series=428 says > "new" > > however, I see patchset is applied (and travis-ci is somewhat broken) > > > > are all paches applied already ? > > Patch status is communicated via the list - and my comments can be > nicely seen when clicking on each individual patch. > it is complicated to view every patch and it's comments. is there a way to change status to "applied" on patchwork ? > > Most patches have been applied, 5/7 has not, and some of the other > code needs polishing. > > gert > > -- > "If was one thing all people took for granted, was conviction that if you > feed honest figures into a computer, honest figures come out. Never > doubted > it myself till I met a computer with a sense of humor." > Robert A. Heinlein, The Moon is a Harsh > Mistress > > Gert Doering - Munich, Germany > g...@greenie.muc.de > ___ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
Re: [Openvpn-devel] state of sitnl patchset ?
Hi, On Mon, Jun 10, 2019 at 12:05:52AM +0500, ?? wrote: > https://patchwork.openvpn.net/project/openvpn2/list/?series=428 says "new" > however, I see patchset is applied (and travis-ci is somewhat broken) > > are all paches applied already ? Patch status is communicated via the list - and my comments can be nicely seen when clicking on each individual patch. Most patches have been applied, 5/7 has not, and some of the other code needs polishing. gert -- "If was one thing all people took for granted, was conviction that if you feed honest figures into a computer, honest figures come out. Never doubted it myself till I met a computer with a sense of humor." Robert A. Heinlein, The Moon is a Harsh Mistress Gert Doering - Munich, Germany g...@greenie.muc.de signature.asc Description: PGP signature ___ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
Re: [Openvpn-devel] [PATCH 2/2] Allow repeated cycles through remotes when management-query-remote is in use
Ref: https://patchwork.openvpn.net/project/openvpn2/list/?series=201 Hi, These patches were meant to help implement choosing the remote through the GUI. I may not find time for that but the patches by themselves are still relevant. If there is some interest I'll rebase to master. Selva ___ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
[Openvpn-devel] state of sitnl patchset ?
Hello, https://patchwork.openvpn.net/project/openvpn2/list/?series=428 says "new" however, I see patchset is applied (and travis-ci is somewhat broken) are all paches applied already ? cheers, Ilya Shipitsin ___ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
[Openvpn-devel] [PATCH applied] Re: Copy one byte less in strncpynt()
Patch has been applied to the master branch. (I have left the "maxlen-1" as it was, as uncrustify says this is fine and I personally find "maxlen - 1" less readable here. I did fix the tab-vs-spaces violation) commit bebd25a0e3a2aba0b1f98463a87b24db6c419a66 Author: Gert Doering Date: Sat Jun 8 09:56:22 2019 +0200 Copy one byte less in strncpynt() Signed-off-by: Gert Doering Acked-by: Antonio Quartulli Message-Id: <20190608075622.11589-1-g...@greenie.muc.de> URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg18502.html Signed-off-by: Gert Doering -- kind regards, Gert Doering ___ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
