On Sat, Nov 26, 2011 at 5:14 PM, David Woodhouse <dw...@infradead.org> wrote: > On Fri, 2011-11-25 at 08:24 +0800, Antonio Borneo wrote: >> no reason, should be applied. >> I'll commit it in the weekend. > > If you don't want to just delete vpnc-script from the vpnc repo, then it > would be best to pull in *all* the fixes from the git tree rather than > diverging.
Hi David, for openvpn the script vpnc-script is one of the possible options. It is acceptable to have it on a separate repository. For vpnc, the script is a mandatory component. I prefer keeping it inside the same repository. I would like to pull all the fixes from your repository and I'm checking all of them. I have some concern about IPv6 patches. So far vpnc doesn't have real support for IPv6. Just few macro definition and a check in the script. Should we consider these patches as a early IPv6 support in the script, waiting for contribution in the core code? Are they required by systems configured for IPv6 and running current vpnc? > In fact, if you want to convert the vpnc repo from Subversion to git, it > would then be easy to automatically pull in the changes from > vpnc-scripts.git. I can help you with that (and give you somewhere to > host it) if it helps. Locally, I already run all my development on git through git-svn. No problems to pull in from your tree. Ragards, Antonio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
