Matthias Andree wrote:
> > Having the branch in git allows iterating over the commits with
> > great ease.
>
> let's not waste time discussing this over and over
I'm sorry I wasted your time.
//Peter
Am 10.12.2010 09:44, schrieb Peter Stuge:
> Adriaan de Jong wrote:
>> > I'd use git for the patches right away anyway,
>>
>> I'm afraid that we started off development based on checked out
>> sources (quite a long time ago). I'll start rebasing to git as soon
>> as I've heard that the git tree is
Adriaan de Jong wrote:
> > I'd use git for the patches right away anyway,
>
> I'm afraid that we started off development based on checked out
> sources (quite a long time ago). I'll start rebasing to git as soon
> as I've heard that the git tree is stable.
By git I don't mean the very latest cont
> Adriaan de Jong wrote:
> > > > About the whitespace: it's a tad difficult to split the patches
> > > > now. Are you sure it wouldn't be acceptable this way?
>
> Peter Stuge wrote:
> I may have misunderstood this. (I read "now" as "this late", but I
> guess maybe you meant "this early".)
>
You re
Adriaan de Jong wrote:
> > > About the whitespace: it's a tad difficult to split the patches
> > > now. Are you sure it wouldn't be acceptable this way?
I may have misunderstood this. (I read "now" as "this late", but I
guess maybe you meant "this early".)
> > I'd suggest that we primarily do co
> -Original Message-
> From: David Sommerseth [mailto:openvpn.l...@topphemmelig.net]
> Sent: vrijdag 10 december 2010 8:56
> To: Adriaan de Jong
> Cc: Peter Stuge; openvpn-devel@lists.sourceforge.net
> Subject: Re: [Openvpn-devel] [Patch] OpenVPN PolarSSL Supp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/10 08:38, Adriaan de Jong wrote:
> About the whitespace: it's a tad difficult to split the patches now. Are you
> sure it wouldn't be acceptable this way?
If I'm not entirely mistaken, these patches are based against a 2.1.x
release and not
Adriaan de Jong wrote:
> Thanks, I'll change the configure options when I rebase the patches
> to 2.2 . I'm a little more familiar with cmake, thanks for pointing
> that out.
Great.
> About the whitespace: it's a tad difficult to split the patches now.
Simple with git. Check out how to do an in
aan
> -Original Message-
> From: Peter Stuge [mailto:pe...@stuge.se]
> Sent: vrijdag 10 december 2010 7:25
> To: openvpn-devel@lists.sourceforge.net
> Subject: Re: [Openvpn-devel] [Patch] OpenVPN PolarSSL Support Preview
> [7/8]
>
> Adriaan de Jong wrote:
> Con
Adriaan de Jong wrote:
Content-Description: 07_polarssl_addition.patch.gz
> Add PolarSSL support to OpenVPN
> +++ b/configure.acWed Dec 08 12:35:42 2010 +0100
> @@ -273,14 +273,16 @@
> )
>
> AC_ARG_WITH([ssl-type],
> - [ --with-ssl-type=TYPE Build with the given SSL library, TYPE = ope
Patch #7 in the series, adds PolarSSL support.
Note that PolarSSL support is against an as-yet-unreleased version of PolarSSL.
The new version should be released somewhere in January/February.
07_polarssl_addition.patch.gz
Description: 07_polarssl_addition.patch.gz
11 matches
Mail list logo
