Hi,
On Thu, Feb 04, 2010 at 04:58:51PM +0100, David Sommerseth wrote:
> > I'd add another rule
> >
> > - All new code must be written following the OpenVPN coding conventions
> > (code indenting, scratch memory handling with "gc", etc.)
> >
> > Long-term maintenance of code written wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/02/10 15:29, Gert Doering wrote:
[snip]
>> - Patches on the mailing list should preferably be start with [PATCH]
>> in the subject field. (This will not cause a direct rejection, but
>> I might miss a contributed patch when parsing the
Hi
I wanted to make redundant VPNs by using multiple instances from same
client to same server but current (2.1.1) implementation of OpenVPN
override previous iroute definition when new client connects with same
ip or same route.
Attached is a proposed patch to allow for multiple paths for the sa
Hi,
On Thu, Feb 04, 2010 at 10:49:23AM +0100, David Sommerseth wrote:
> I am willing to maintain a testing tree,
Thanks. This is quite an important role, and I was refraining from
volunteering because I *know* I don't have enough time.
> but to make it maintainable and
> flexible for my ideas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/01/10 12:09, Samuli Seppänen wrote:
> Hi all,
>
> I discussed the main development process of OpenVPN with James and a few
> community developers in the IRC. This is what I ended up with:
>
> http://users.utu.fi/sjsepp/openvpn/getting_code_to_o
Hi all,
It's soon time for our weekly meeting:
Place: #openvpn-discussion at irc.freenode.net
Time: Thursday Feb 4th 19:00 UTC (20:00 MET, 21:00 EEST, 11AM PST, 2PM EST)
Duration: ~60 min
Topics:
- defining and agreeing upon the basic development workflow
- use and purpose of stable, bugfix an
