This mailing list is mainly used for the developers. If you wish to discuss something technical about tinc, you can do it on this list. ()

Daniel Schall | 3 Jan 2011 19:01

Tinc improvements

Dear Guus,

I've attached my first git commit to your repository.
It does not contain any new functionalities, but it is a first try to
interact with your git copy.

Could you please verify, if you can push this commit to your repository?
If it works, I'll send you the rest of my work, which contains:

1) some small improvements in logging
	(using flags instead of counters)

2) the multicast announcement stuff we talked about in the last months

3) an improved PMTU discovery with predictable packet sizes for the
probe packets

By the way, I've re-formatted the code to better suit your coding style.

Best,

Daniel

commit 50a9f9c9d055dbd20d81e7072f4a059e17c68118
Author: Daniel Schall <tinc-devel@...> 2011-01-03 18:46:51
Committer: Daniel Schall <tinc-devel@...> 2011-01-03 18:46:51
Parent: 4b8a5993036fccc2108fcc2550649d9b78fb1ab7 (Update the NEWS.)

add iphlpapi and other headers to have.h and configure.in

(Continue reading)

headers

Guus Sliepen | 5 Jan 2011 14:23

Re: Tinc improvements

On Mon, Jan 03, 2011 at 07:01:46PM +0100, Daniel Schall wrote:

> I've attached my first git commit to your repository.
> It does not contain any new functionalities, but it is a first try to
> interact with your git copy.

It applies. However, try to keep separate issues in separate commits:

> add iphlpapi and other headers to have.h and configure.in
> add flags to vpn_packet

The change to have.h and configure.in for example could be in its own commit.
Also, some more information in the commit message, such as why you want to link
with iphlpapi or what flags you add, would be helpful.

Also, it is better to send patches with "git send-email <previous-commit>",
where <previous-commit> can be a commit ID or an alias like "HEAD^^", and this
will format all the commits after the specified one and email them, such that I
can just pipe the mails through "git am". 

Alternatively, make your git tree publicly accessible, so that I can just pull
from it. Perhaps I can set something up on tinc-vpn.org where people can push
into their own branches...

Anyway, I cannot accept this commit, the added flags to vpn_packet make it
incompatible with previous versions, and there is no fallback option.

> 1) some small improvements in logging
> 	(using flags instead of counters)
>

(Continue reading)