From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/openswan
Date: Mon, 23 Jul 2007 02:45:25 -0700 (PDT) [thread overview]
Message-ID: <20070723094525.6D3AFA65D9@busybox.net> (raw)
Author: ulf
Date: 2007-07-23 02:45:23 -0700 (Mon, 23 Jul 2007)
New Revision: 19211
Log:
Update openswan package with bugfixes
Added:
trunk/buildroot/package/openswan/linux-2.6.20-openswan-2.4.7.kernel-2.6-klips.patch
trunk/buildroot/package/openswan/linux-2.6.20-openswan-2.4.7.kernel-2.6-natt.patch
trunk/buildroot/package/openswan/linux-2.6.20-openswan-2.4.7.kernel-2.6-nfmark-rename.patch
trunk/buildroot/package/openswan/linux-2.6.20-openswan-2.4.7.kernel-2.6-zzz-crypto_alg_available.patch
trunk/buildroot/package/openswan/linux-2.6.20-openswan-2.4.7.kernel-2.6-zzz-void-sock_unregister.patch
Changeset:
Sorry, the patch is too large to include (59595 lines).
Please use ViewCVS to see it!
http://uclibc.org/cgi-bin/viewcvs.cgi?view=rev&root=svn&rev=19211
next reply other threads:[~2007-07-23 9:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 9:45 ulf at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-24 8:56 [Buildroot] svn commit: trunk/buildroot/package/openswan jacmet at uclibc.org
2009-01-16 13:21 jacmet at uclibc.org
2008-12-17 10:32 jacmet at uclibc.org
2007-09-19 9:20 aldot at uclibc.org
2007-09-19 8:50 aldot at uclibc.org
2007-09-18 13:02 aldot at uclibc.org
2007-06-21 22:14 aldot at uclibc.org
2007-06-21 22:09 aldot at uclibc.org
2007-03-24 12:46 aldot at uclibc.org
2007-03-21 10:35 aldot at uclibc.org
2007-02-15 13:54 aldot at uclibc.org
2006-12-22 11:29 aldot at uclibc.org
2006-12-14 15:36 aldot at uclibc.org
2006-11-29 20:51 aldot at uclibc.org
2006-11-29 13:21 aldot at uclibc.org
2006-11-28 17:04 aldot at uclibc.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070723094525.6D3AFA65D9@busybox.net \
--to=ulf@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox